HTMLProtector 3.5 - User Guide and FAQ

Download Site 1       Download Site 2       Download Site 3       Buy Now $39.95

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 HTMLProtector, switch to "Tags to Skip" tab, then press "Add" button and input "" 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: "".
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.

1. Create directory "c:\new_web" in your disk
2. Run HTMLProtector, 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.

1. Please make sure that HTMLProtector v3.0 or later version has been used for your protection.
2. Your remote hosting server needs to be able to execute specified server side script (PHP, ASP or PERL). If you can't be certain of that, please inquiry it from your hosting provider.
3. The generated server side script file "hp_image.php (.asp/.perl)" must be uploaded to the same directory of protected pages.

• Run HTMLProtector 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.
• Run HTMLCompact and compress your protected pages.

Frequently Asked Questions - HTMLProtector

1. Will HTMLProtector destroy all my hard work if I make a mistake when using it?
   This should not happen under most situations -- HTMLProtector offers three kinds of output modes: "Overwrite", "Copy to another directory" and "Create new protected file". The latter to modes will not modify your original file at all, they make a new file. "Overwrite" mode can be dangerous if you are careless, with this mode your original work will be overwritten after protection.
   
   To be safe, follow the following rules:
   1) Don't use "overwrite" mode unless you are 100% certain your changes will be safe;
   2) If you decide to use "overwrite" mode, enable "create backup";
   3) Worst case scenario, if your pages have been encrypted by HTMLProtector and you are unable to recover it for later use, you may send it to our support team and we will help you decrypt them.
   
   
2. I protected a number of pages, and now I do not have original pages. Can I reverse the protected pages?
   If you have enabled "Create backup" option when using "Overwrite mode", you may find a file named as "*.bak" in your protected HTML directory after protection. To reverse the encryption, just rename this .bak file to its original filename.
   
   If these web pages are really very important to you and you can't find any backup in your hand, you can send these files to the developer. And they will try to recover them for you.
   
   
3. Will the text "This webpage is protected by HTMLProtector" still show up on my pages after I purchase HTMLProtector?
   The words like "This webpage is protected by HTMLProtector" 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 HTMLProtector after purchase in 30 days, we will issue refund for your payment as your request.
   
   
4. How does encrypting my page with HTMLProtector effect how search engines see it?
   All search engines will simply ignore the JavaScript code that is 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. Be sure you choose your "encryption mode" on the "Encryption" tab carefully, try and keep the following in mind:
   
   
   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 (including meta keywords, and 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, which would affect your rankings at most extent.
   5) If you want search engine to index content of your pages, you may even set "Encryption Mode" as "Protect None". 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 method in "Meta Tag" and "Script" tabs could still be used to protect your pages.
   
   
5. I am using HTMLProtector 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.
   
   
6. It seems that once a web page is protected using HTMLProtector, 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.
   
   
7. I created new protected pages but the result of the "Test" within the HTMLProtector 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.
   
   
8. Why my pages could not be edited and published by using FrontPage again after protection?
   A page protected by HTMLProtector 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.