Are you calling the PageLocker snippet uncached (with the exclamation point)?
Hi Boy Ray, thanks for your response - this may seem like a very silly question, but where is the pagelocker snippet called - i can't find that out? It has a pagelocker page template and two template variables assigned to the password protected page. Any ideas? Many thanks for your time
My guess is that it would be in the page template(s).
Unfortunately not..... it does seem ridiculous that i can't find it, but it definitely isn't referenced from within the page template. Any ideas anyone!?
Been struggling with this one for a while - are there any other plugins out there for password protecting a single page?
Sorry, I don't know of any. The pagelocker tag would almost have to be in either the template, or in a chunk or TV referenced in the template.
-
☆ A M B ☆
- 24,524 Posts
There is no snippet. It's a plugin, and is based on the template a resource uses. If the resource has a password or a group set in its TV, then PageLocker comes into play, otherwise it doesn't. There's no time involved here, it's a simple yes/no situation. Either a TV is set or it isn't. Actually it's a pretty simple plugin.
If there is a TV value, and the user's submission matches the resource's password, there are a couple of SESSION values that get set. This timing business makes me think that there's something about the session tables causing this, and it's not that the page doesn't require a password, but that the user's SESSION values have been restored.
Sorry about that. The version I found when I looked was a snippet.
https://github.com/aladage/pagelocker