Description
With the protected node module users can restrict access to a node with a password they provide when creating the node (or a site wide password or a per node type password.) On node creation authorized authors can protect a node by supplying a password and verify strength of the password via JavaScript.
People who want to view the node or download one of its private attachments are first redirected to a password query page (/protected-node). Once the user entered the right password, he is redirected back to the original node. Authorizations are stored in sessions, so users don't have to enter the password over and over again once provided (requires cookies.)
Detailed info in the Protected Node Documentation
Advanced enhancements in 6.x-1.x and 6.x-1.6
Note: 1.6 is the new official version. It was tested by about 60 people.
First, if you want to be able to go back, make sure to first backup your database. This update makes changes to the database to better support the module features.
The module was fixed so it is more secure as expected on Drupal.org (i.e. protected nodes do not appear in lists, searches, etc.)
Nodes that are not accessible by someone now return an immediate Access Denied instead of a 302 + Access Denied.
The 302 does NOT make use of a $_SESSION variable anymore. Instead, it uses a $_GET variable which is much lighter overall and extensible.
The settings include MUCH more information. It has statistics, security entries, protected node data, and "mass functions" (be VERY careful with those!)
The security features include a way to define the default settings of the "Show title" flag and offers a global password (for those of you who want to protect many nodes with the same password.) I also added a per node type password. In other words, you could create a node type named "secure_stuff" and assign a node type wide password so all those nodes of type secure_stuff will make use of that default password.
Also, there is now a callback to let other modules hide their own data from nodes (i.e. CCK could hide its fields when a node is marked protected and the password was not specified -- note that somehow CCK fields are not shown anyway.)
For those who upgrade the module to version 6.x-1.5
Download: http://drupal.org/node/386604
This release contains a regression. The protected node admin page no longer contains the node type selection control. This represented a duplicate functionality with access control and have been dropped in favor for permissions for roles. After upgrade, please go to permissions and give your role at least access to view protected content.
Version 5.x
Note that version 5.x is not being supported. There seems to be a few problems with it for some people. You may want to look at closed issues as some may include a solution for your problem. Creating a new issue for 5.x is probably not going to get you anywhere.
Known conflicts:
Project Information
- Maintenance status: Actively maintained
- Development status: Under active development
- Module categories: Content Access Control, Content Display, Security, User Access & Authentication
- Reported installs: 1355 sites currently report using this module. View usage statistics.
- Last modified: January 25, 2012
