Q: Will HTMLProtector destroy all my hard work if I make a mistake when using it?
A: 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.

Q: I protected a number of pages, and now I do not have original pages. Can I reverse the protected pages?
A: 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 may send these files to me. Our developer will try to recover them for you.

Q: Will the text "This webpage is protected by HTMLProtector" still show up on my pages after I purchase HTMLProtector?
A: 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 upon your request.

Q: How does encrypting my page with HTMLProtector effect how search engines see it?
A: 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 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 method in "Meta Tag" and "Script" tabs could still be used to protect your pages.

Q: 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?
A: 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.

Q: 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?
A: 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.

Q: 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.
A: 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.

Q: How does HTMLProtector work with FrontPage?
A: To make HTMLProtector 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 HTMLProtector 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 HTMLProtector, 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 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.

Q: Why my pages could not be edited and published by using FrontPage again after protection?
A: 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.

Q: Can single license of HTMLProtector be allowed to protect multiple pages, or multiple websites?
A: Single license can only allow you to install HTMLProtector 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.

Q: How could I get the feature "Protect image by using server side script" to work?
A: This option will prevent your images from being saved in web browser cache. To make it work work, please:
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.

Q: Which options should be enabled to protect images of my website?
A: With current version of HTMLProtector, 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.

Now HTMLProtector also includes more advanced image protection options, which include:

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.

All these methods can take further steps to prevent people from stealing your images effectively under most conditions.

Q: Is it possible to encrypt a section of HTML code in a page rather than the entire contents of the body tag?
A: Yes. The "partial encryption mode" of HTMLProtector 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 HTMLProtector 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.

Q: Which process should be taken to use both of HTMLProtector and HTMLCompact with a web page?
A: If you want to both protect and compress your pages, we suggest you follow steps as below:

1) 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.
2) Run HTMLCompact and compress your protected pages.

By doing that, your will make your pages both be compressed by HTMLCompact and protected by HTMLProtector. Also, it will generate a smaller and faster-load page, compared with the page you got before.

Q: How to protect .shtml files by using HTMLProtector?
A: To work with your .shtml files, please choose "Server-side Include Page" for "File Type" option within "Input" tab before protection process.

Q: Will HTMLProtector prevent screen capture software from capturing my web pages that are displayed on the screen?
A: HTMLProtector 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".

Q: How to make "Location Lock" and "Referrer Lock" options work?
A: "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.

Q: When I access protected web pages, I can't copy and paste text with any other application.
A: 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.

Q: I want to be able to enter the password once for the login page and then the links will jump me to the other pages without having to retype the password for each page. How can I do that?
A: A new feature "Remember password on successful login" has been added with HTMLProtector version 3.5. If the option is enabled, username and password will be saved into session cookie on successful login and visitor will not need to enter them again when opening other pages protected by using same username and password.

Q: 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?
A: This problem was because that you enabled "Disable adobe acrobat web capture" option during protection. To make Adobe Acrobat 6 stop working, HTMLProtector will add a not-existing CSS file "hp_null.css" reference into protected pages, which caused these 404 errors in your web log.

Q: I have been unsuccessful in trying to upload a protected web page to Yahoo Geocities. The file manager repeatedly displayed "invalid file" message. What am I doing wrong?
A: As we know, there are three possible methods can be applied to solve the upload problem with Yahoo Geocities.

1) Upload your protected files by using FTP software. Your FTP account information is listed in "File Management Tools" of your Geocities account. To get detailed information about FTP uploading, you may also read help manual at http://help.yahoo.com/help/us/geo/gftp/.

2) The problem only occurs with Yahoo SiteBuilder. To avoid it, please upload your protected files by using Yahoo PageBuilder instead of Yahoo SiteBuilder, which can be accessed at http://geocities.yahoo.com/v/pb.html.

3) The following is contributed by Sid Paskowitz: "I used WordPad to highlight and copy the encoded protected page code to my electronic clipboard in Windows, opened the Geocities file manager, edited the current .htm page that I wanted to replace (I deleted all the current content), and then I pasted the content of the electronic clipboard to that page and saved it. The encoded page worked properly. (Note: if a current page/file with the desired name does not exist, the file manager can be used to create it by copying an existing page.)"

Q: After protecting of my ASP pages, I found that I still can read the ASP codes. Did I make something wrong?
A: By design, the basic principle of HTMLProtector is converting static HTML source code into unreadable JavaScript string. Although it really supports dynamic web pages (ASP/PHP/JSP/etc), all dynamic script codes within the page will be skipped during protection process. This means that you still can see all of your script codes untouched in protected page, which must be done to makes protected dynamic page be parsed and executed by web server correctly.