Made to Order Software Corporation - protected

Protected Node Rules Support

Alexis Wilke — Thu, 22 Mar 2012 00:26:28 +0000

The following features are available only when installing the Rules extension of protected nodes. This extension requires the thrid party Rules extension for Drupal.

Protected Node Rules Conditions

When handling a Node, it is possible to check whether the node is currently protected or locked.

Protected Nodes

A node is said protected when the node was protected by a password using the Protected node module.

Whether the user can view that node is irrevelant in this case. Only the fact that the node requires a password to be viewed is what this condition checks.

Locked Nodes

A ...

Protected Node Views Support

Alexis Wilke — Wed, 22 Feb 2012 07:41:01 +0000

The Protected Nodes offers some additional supports to views 2.x and 3.x in Drupal 6.x.

The additional support includes fields, filters, and sort capabilities that are added to the Node type. The join between the regular node and the protected node data is the node identifier (nid). This means the revision identifier is ignored.

Password last changed

This value is the date when the password was last modified. You can display this date, filter using the date, and sort by date.
Node is protected

This value is a yes/no value (i.e. Boolean) which can be ...

Protected Node per Node Type Settings

Alexis Wilke — Mon, 06 Jun 2011 21:08:51 +0000

Node Type extension

The Protected Node module adds a field set to the Node Type form that you edit under:

Administer » Content management » Content types

These additions are explained in detail below.

The main reason for adding this feature is to avoid seeing the field set on all the node edit forms. With this feature you can hide the form on all the node types that you will never protect with a password.

Protected mode for nodes of this type

This option let you choose how this node type handles the Protected Node capability.

Never protected

This means this node type is

Protected Node Password Fork Feature

Alexis Wilke — Thu, 28 Apr 2011 04:21:32 +0000

Password Fork

The new module allows for a password fork.

This means you can send your users to one specific page, and tell them about a password to use on that one page. Depending on the password, they will be sent to one of several nodes.

This works in a very similar way as the other password form, except that there is no specific destination, and the users need to know any one of the passwords.

The feature uses a specific URL defined as follow:

/protected-nodes?protected_pages=<nid1>,<nid2>,...&back=<url>

protected_pages=<nid1>,<nid2>,...

This

Protected Node Password Form

Alexis Wilke — Thu, 28 Apr 2011 03:54:56 +0000

Protected Node Password Form

Once a node is protected, users who cannot bypass the password are sent to the password form (see image on the side.)

The password form is very simple. It includes one field for users to enter the node password and an OK button.

When the browser of the user sent us a referrer, then the Protected node module adds a Cancel link back to that referrer. Using the global settings, you can force a Cancel link to always be there. When no referrer is available, the Cancel link will send your users to your home page.

The title, information, description and title over the

Protected Node Password Field set

Alexis Wilke — Thu, 28 Apr 2011 03:14:49 +0000

Once installed and properly configured, the Protected node module adds a field set in the node edit form (assuming the user has the corresponding permission: "edit any password" or "edit password <node type>".)

This field set includes two flags, a password, and emails (optional.)

By default, the field set is closed unless you selected protected by default. Whether the field set should be opened or closed can selected in the node type settings.

The <node type> is protected

The first check box is used to password

Protected Node Global Settings

Alexis Wilke — Thu, 28 Apr 2011 00:49:24 +0000

The protected node module has global settings found under:

Administer » Site configuration » Protected node

Protected node Statistics

The page starts with statistics to let you know how pages are protected on your website. All the counts include published and unpublished content.

Total nodes — the total number of nodes on your website
Unprotected nodes — number of nodes that do not have a password
Protected nodes — number of nodes that are current protected by a password
- Showing title — number of nodes showing their title

Protected Node Permissions

Alexis Wilke — Thu, 28 Apr 2011 00:18:20 +0000

The Protected Node module adds permissions to define who has the right to make use of the password feature.

access protected content

This is the basic access permission for users. Users who are given this permission can access a protected node as usual, except that they need to enter the password to handle the node.

This is true whether they want to view, edit, delete the node.

bypass password protection

Users with the bypass permission can access all nodes that are protected without having to enter the passwords. This is very handy for website administrators and

Protected Node Installation

Alexis Wilke — Wed, 27 Apr 2011 23:56:31 +0000

The basics of the Protected Node installation are easy:

Get one of the tarball from Drupal.org
Extract the files under sites/all/modules or some other modules folder
Go to Administer » Site building » Modules and install the module (package Access)
As the administrator (UID = 1) you are done.

Once you have installed the module, you probably want to change the permissions. Permissions allow your users to access the Protected Node functionality based on their roles. Please, see the point about Permissions for more information about those.

Now, you're ready ...

Protected Node (The Drupal module —)

Alexis Wilke — Wed, 27 Apr 2011 23:39:02 +0000

The Protected Node module is used on websites where some pages need to be password protected. This is different from asking someone to create an account and often seen as much more user friendly, although in terms of protection it is quite similar.

If you've seen photo websites where you can go to an album but have to enter a password to see the photos, that's one example how this module can be used.

The module adds a field set in the node form to let authors enter a password.

The module has many options that are rather tricky to use so this documentation tries to explain what you can do