This plugin adds optional per-page user name and password protection, implemented using standard HTTP protocol authorization headers, thus triggering the standard user\/password dialog of the browser, and making it possible to make the browser store the credentials.<\/p>\n\n
Subpages of a protected page are protected with the same user name and password as their parent.<\/p>\n\n
Protected pages and their subpages do not show up in menus, search results and page lists.<\/p>\n\n
Copyright (c) 2009 Morten H\u00f8ybye Frederiksen morten@wasab.dk<\/a><\/p>\n\n Permission to use, copy, modify, and distribute this software for any\npurpose with or without fee is hereby granted, provided that the above\ncopyright notice and this permission notice appear in all copies.<\/p>\n\n THE SOFTWARE IS PROVIDED \"AS IS\" AND THE AUTHOR DISCLAIMS ALL WARRANTIES\nWITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF\nMERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR\nANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES\nWHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN\nACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF\nOR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.<\/p>\n\n\n See also the usage instructions<\/a>.<\/p>\n\n\n Not really, no. It depends on WordPress working as intended, and the user name and password is sent in clear text across the wire.<\/p><\/dd>\n No, only pages and their subpages can be protected by this plugin.<\/p><\/dd>\n Yes, that's actually considered a feature (at least for now). The point being, that a hidden page really doesn't need to be protected, and that it makes it work cleaner for e.g. members-only pages. Don't worry, as you have probably discovered, the contents of the page are not visible without the correct user name and password.<\/p><\/dd>\n You might be running WordPress on PHP using CGI, and that often makes it impossible to handle the authorization features of HTTP - the appropriate headers simply don't get passed on to PHP\/WordPress by the web server.<\/p>\n\n If you wan't to make sure that's the problem, try creating a protected post with a user name and password of debug\/debug.<\/p><\/dd>\n Great, thanks! Please do leave a comment on the plugin's homepage\nwww.mfd-consult.dk\/page-protection<\/a> or send an e-mail with details; I'll\nmake sure it's included in the next version.<\/p><\/dd>\n\n
wp-content\/plugins\/<\/code>.<\/li>\n\n