The following features are available only when installing the Rules extension of protected nodes. This extension requires the thrid party Rules extension for Drupal.
When handling a Node, it is possible to check whether the node is currently protected or locked.
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.
A ...
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.
This option let you choose how this node type handles the Protected Node capability.
This means this node type is
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 first check box is used to password
The protected node module has global settings found under:
Administer » Site configuration » Protected node
The page starts with statistics to let you know how pages are protected on your website. All the counts include published and unpublished content.
The Protected Node module adds permissions to define who has the right to make use of the password feature.
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.
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
The default Aggregator Drupal module does not work very well. There are several problems with the Drupal Core module, one of which we have not fixed in our version (i.e. the flatness of the item table.)
There is a list of the known issues and our comments and whether we fixed the problem:
| Problem | Solution in m2osw's version of Aggregator |
|---|---|
| Missing XML marker | The <?xml ... ?> marker is missing from some RSS feeds, add it as required |
| Spurious ... |
One of the options to link terms in a vocabulary to their view is:
taxonomy_view/voc-xxx/term-xxx
This option sends you to that path, exactly (where voc-xxx and term-xxx are numbers representing the vocabulary identifier and term identifier respectively.)



Snap! Blogger Pro. It's the best decision you made all day.
Your blog is you online. Be known by the writing in your journal, talk about your likes and dislikes, either way, blogs are a must have in the 21st century!
PLEASE NOTE: This product upgrades your
Snap! Blogger Lite to
Snap! Blogger Pro.
Snap! Blogger Pro websites come with the following features: