EyesOnly (supplied with Password Protect 6)

There are several ssues you will want to read about here. They relate to use in Templates and their Children, and also to Flash content on the page.

 

1) If EyesOnly is on a Template, EyesOnly is not clever enough to prevent you from applying it again to the Template's Child. So just don't do it.

2) If you are able to use the SSI option and are adding EyesOnly to a Child page of a Template - if a user has disabled Meta Redirects, then it is each Editable Region in the Body that will be blanked. The user will get to see the NonEditable regions, so they ought not contain sensitive material. If it is important to protect against the user seeing even the content in NonEditable regions, then you should instead be adding EyesOnly with SSI Protection, to the primary Template itself (which optimally protects all its children).

3) As described on the Details page, if your server does not support SSI, EyesOnly adds a layer to hide your page content - useful if a user has turned off javascript and for some mac browsers that would otherwise reveal your page for 1-2 seconds before redirecting away from it. The problem is if you have Flash content on your page - it will be revealed right though the hiding layer - so despite the erstaz 404 message and the otherwise blank screen, the Flash will be visible as well. This is not good, but the alternative (since your server does not support the SSI option which is preferred anyway) is to not hide the page at all - so altho not perfect in the face of Flash, it is still far better than nothing.

Back to Password Protect 6