What if I will make a mistake using HTML Protector? HTML Protector offers three types of output modes: "Overwrite", "Copy to another directory" and "Create new protected file". The last two modes will not modify your original file at all, they make a new file. We recommend to follow these rules: 1) Don't use the "overwrite" mode unless you are 100% sure that your changes are safe for an original file(s); 2) If you decide to use the "overwrite" mode, make sure to enable the "create backup" option; 3) The worst scenario: your pages have been encrypted by HTML Protector and you are unable to recover it for later use. In that case you can send them to our support team and we will help you to decrypt them.
Can I reverse the protected pages? If you have enabled "Create backup" option when using "Overwrite mode", you can find a file named as "*.bak" in your protected HTML directory after the protection. To reverse the encryption, simply rename this .bak file to its original name.
Webpage encryption & search engines The search engines will simply ignore the JavaScript code added to your
page, so all the options in "Meta Tag", "Script", and "Source Code" tabs won't
affect your search engine ranking at all. Make sure to choose your "encryption mode" on the "Encryption" tab carefully:
1) "Protect email links" should have no effect on your search engine rankings;
2) "Protect all links" will make search engine spiders unable to follow the
links on your pages, but it should not affect the ranking of the page; 3) "Protect BODY section" will cause search engine spiders to not be able to
index the content between BODY tags. But all content between HEAD tags (meta
keywords, etc...) will be kept untouched after encryption process. In that case,
search engine bots can still read all meta tags of your protected page without
any problem. 4) "Protect Entire Page" will cause search engine spiders to not be able to
index the page totally. If you want search engine to index the content of your pages, you can even set
"Encryption Mode" as "Protect Nothing". With this mode, the source code of your
pages will not be encrypted so that search engine bots can index the content as
before. But other protection methods in the "Meta Tag" and "Script" tabs could
still be used to protect your pages.
Will the text "This webpage was protected by HTML Protector" still show up after I purchase HTML Protector? The words like "This webpage was protected by HTML Protector" are only available with unregistered version. It will not be added to protected pages with registered version after protection. We offer unconditional 30-days money back to all purchases. If you dislike HTML Protector after purchase in 30 days, we will issue refund for your payment as your request.
I am using HTML Protector and find it to be great. However, the source code can still be read using Netscape. Is there anything I can do about this? To protect your source code from being seen using Netscape Navigator 4.XX, you should enable "Make page expire immediately" in "Meta Tag" tab before starting protection.
It seems that once a web page is protected using HTML Protector, the ability to e-mail from that protected page no longer works. Can you please explain why that happens? The reason you are having this problem is the fact that some e-mail clients have JavaScript support disabled when viewing HTML e-mails. For example, Outlook Express' default "Security Zone" is set to the "Restricted sites" setting. This setting will prevent Outlook Express from allowing the JavaScript to decrypt your encoded HTML.
I created new protected pages but the result of the "Test" within the HTML Protector was a URL of "about:blank", and a blank page displayed in the browser. It seems that you have a feature like "Disable Off-line Viewing", "Location Lock" or "Referrer Lock" enabled for your protection. If these options are chosen, you will only view blank page when opening protected pages locally by clicking "Test" button within "Result" tab. To test these protected pages, you should upload them to your web server and test them remotely.
How does HTML Protector work with FrontPage? To make HTML Protector work with FrontPage correctly, please follow instructions as below: "FrontPage extension (Web Component)" is used with your web pages: To summarize, when you include "FrontPage extension" into a web page, FrontPage changes the saved HTML code before it publishes the page to the remote server, eliminating the local path references. You must first publish the page to the Web with FrontPage, and then you must download the source of the page back to your hard drive, and then use HTML Protector to encrypt that page and upload that page to the site. Otherwise, the paths will be wrong and the counter will not work. 1) Publish original pages to the remote server by using FrontPage. 2) Download all of your original pages back by using a FTP software program, and save them into a different directory from your FrontPage project, let us say, "c:\new_web". 3) Run HTML Protector, switch to "Tags to Skip" tab, then press "Add" button and input "<!--webbot" as "Starting Tag" and "-->" as "Ending Tag" (Note: no double quotation marks needed when you are inputting). If you are using FrontPage extension to save form result, you should also add another tags pair: "<form" and "</form>". 4) Protect your saved page in "c:\new_web". And upload protected pages back to your remote server and overwrite original pages by using FTP program.
"FrontPage extension (Web Component)" is not used with your web pages: 1) Create directory "c:\new_web" in your disk 2) Run HTML Protector, switch to "Output" tab, check "Copy to the following directory", specify "c:\new_web" as "Directory" 3) Do other settings as you like and start protection 4) After protection, you will find all new protected files in directory "c:\new_web" 5) Copy other non-HTML files into this new directory 6) Upload protected pages to your web and replace original pages with them by using FTP program.
Why my pages could not be edited and published by using FrontPage again after protection? A page protected by HTML Protector can't be edited by HTML editors (FrontPage, DreamWeaver, etc) directly. To modify the content of this protected page, you should modify the backup copy the original page, and protect it again. To solve this problem in better way, you may choose "Copy to the following directory" in "Output" tab as "Output" mode and specify another directory to store new protected pages. During protection process, protected pages are generated in the directory you specified with same name of original pages. After protection, you also need copy other non-HTML files into this directory and upload all of them to your remote server.
Can single license of HTML Protector be allowed to protect multiple pages, or multiple websites? Single license can only allow you to install HTML Protector on one computer, but it may be used to protect web pages of unlimited number of web sites. So we think only one license should be purchased for all of your websites.
How could I get the feature "Disable image caching in browser by using PHP" to work? To make "disable image caching in browser by using PHP" option work, please: 1) Your remote hosting web server should support PHP. If you can't make sure about that, you may inquiry from your hosting provider. 2) The file "hp_image.php" generated by HTML Protector should be uploaded to the same directory of protected pages. 3) Due to a known bug, this option doesn't work on server with PHP 4.2 or later version installed. If version of PHP on your server is 4.2 or later, please contact us to get a pre-release upgrade version to fix this problem.
Which options should be enabled to protect images of my website? With current version of HTML Protector, instructions as below may be chosen to protect your images at maximum extent: Encryption Mode: Use "Protect BODY section" or "Protect entire page". Script: Enable options include "Disable right mouse click", "Disable text select", "Don't display links in status bar", "Disable page printing", "Disable clipboard and printscreen", "Disable drag and drop", "Disable adobe acrobat web capture" and "Disable Opera user". Image: Enable "Disable image caching in browser by using PHP", if your web server supports PHP. Server-side script call: Convert image link to PHP, ASP or PERL call; Flash protection: Convert image to Flash movie; Image splitting: Split image into small pieces; Watermark: Add watermark to image.
Is it possible to encrypt a section of HTML code in a page rather than the entire contents of the body tag? Yes. The "partial encryption mode" of HTML Protector may satisfy your need. If you want to encrypt only a part of the code, you have to enclose it within these html comment tags (case insensitive): <!--hpstart--> ... here comes the part of the code you want to encrypt <!--hpend--> After modified your original page, please use HTML Protector to protect it again and check the result. Please note: you should select "Protect nothing" as the "Encryption Mode" to make this "partial encryption mode" work.
Which process should be taken to use both of HTML Protector and HTML Compact with a web page? If you want to both protect and compress your pages, we suggest you follow steps as below: 1) Run HTML Protector first. Switch to "Encryption" tab, choose "Protect nothing" as "Encryption mode", and enable other protection options as you like. Then protect your original pages and get protected pages. 2) Run HTML Compact and compress your protected pages. By doing that, your will make your pages both be compressed by HTML Compact and protected by HTML Protector. Also, it will generate a smaller and faster-load page, compared with the page you got before.
How to protect .SHTML files by using HTML Protector? To work with your .SHTML files, please choose "Server-side Include Page" for
"File Type" option within "Input" tab before protection process.
Will HTML Protector prevent screen capture software from capturing my web pages that are displayed on the screen? HTML Protector has "Disable printscreen and clipboard" option, but it only works with Internet Explorer 4+ (Windows). The principle of this option is fairly simple: clear the content of clipboard periodically. If visitor tries to copy the screen by pressing "Printscreen" key on keyboard, he will fail. But it still can't stop him from using screen capture software like "Print Screen Deluxe" and "SnagIt".
How to make "Location Lock" and "Referrer Lock" options work? Location Lock is used to limit where your page should be placed. If your page will be allowed to place within www.mysite.com, you should enter "www.mysite.com" into "Domain/URL Address" of "Location Lock" option; If your page will only be allowed to place at http://www.mysite.com/mypage.htm, you should input "http://www.mysite.com/mypage.htm" instead. Referrer Lock used to limit where your page should be linked. If your page will be allowed to link from any page within www.othersite.com, you should enter "www.othersite.com" into "Domain/URL Address" of "Referrer Lock" option; If your page will only be allowed to link from http://www.othersite.com/otherpage.htm, you should input "http://www.othersite.com/otherpage.htm" instead.
When I access protected web pages, I can't copy and paste text with any other application. If a web page which is protected with "Disable clipboard and printscreen" option enabled is opened in web browser, it will disable all system clipboard operation, such as "Copy" and "Paste". To fix this problem, please close web browser or unload this protected page.
After protecting my files I am getting numerous 404 errors in my access
log with a command of "GET path/hp_null.css" with path being the path to the
html file. Can you explain this please? That's because you enabled "Disable adobe acrobat web capture" option during
protection. To make Adobe Acrobat 6 stop working, HTML Protector will add a
not-existing CSS file "hp_null.css" reference into protected pages, which caused
these 404 errors in your web log. |