About PageLocker

PageLocker provides simple front-end password protection for individual or groups of pages.

By setting a password in a page's template variable (and optionally setting a password group to allow single-password access to a series of pages), site editors and admins can provide basic password protection without the use of ACLs.

Information

Released
July 24, 2012

Supported Database
MySQL

License
GPLv2

Supported Versions
2.2 - <3.0

Downloads
2,853

Instructions

  • Install PageLocker through Package Management.
  • Create a new resource, and assign it the "PageLockerFormTemplate" template. Click save, and make a note of the resource's ID. This template can be customized as much as you want, so long as the form within it contains a password field named "password". NOTE: this template should ONLY be used for the form page, and not for any other pages (including your protected pages).
  • Open the PageLocker plugin, and on the "Properties" tab, unlock the default properties and enter the resource ID from Step 2 as the value for "formResourceID". NOTE: The plugin will not work without a value set for this property.
  • Create two new template variables, named "pagePassword" and "pagePasswordGroup" (if you use different names, you must also change the plugin's corresponding property values). "pagePassword" should have a text input type. "pagePasswordGroup" should ideally be either a text, tag or listbox input type (a listbox can help control the names of your password group names). Assign these two TVs to whatever templates need password protection.
  • Go to the individual page you want to protect, and fill in a password. Optionally, choose a group. Users who successfully enter a password for a page will be able to enter any other pages within the same group without re-entering a password.
  • New in 1.1.0-beta1

    1.1.0-beta1-- Resolved potential E_NOTICE warnings caused by unset $_POST and/or $_SESSION variables (courtesy of Bob Ray)-- Refactored slightly to eliminated potential infinite loop when the plugin is installed incorrectly.

    1.0.0-beta1:-- Initial release

    Current releases

    1.1.0-beta1
    View | Download
    July 24, 2012
    2.2 - <3.0