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.
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.
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.)
A security issue was found in all versions of jsMath before 2.x-dev for Drupal 6.x of Jul 29, 2010.
You may still securely use older versions of jsMath on private websites and websites were you are the only user (as in, the only one who can log in.)
The Drupal Security Advisory issue is here: http://drupal.org/node/854402
Go to Administer » Site building » Modules and click on To Do Views to install the Views extension for the To Do module.
This module requires the installation of the 3rd party Views module.
The following are screenshots demonstrating the capabilities of the To Do List module.
Screenshots are clickable to review the large version (scale 1:1).
This page documents the usage of the To Do List module to end users (i.e. not how to install and setup the module, but how to create To Do List items, share them, mark them started/finished, etc.)
For administrative information check out the To Do List module help.
Install the module as usual, generally under your sites/all/modules folder. On a Unix command line, you can use the tar tool like this:
cd sites/all/modules tar -xf to_do.tar.gz
Then go to Administer » Site building » Modules and enable the To do list module.
Once installed the module offers several permissions under Administer » User management » Permissions (admin/user/permissions). These are include permissions similar to the Node permissions and some others. All the permissions are explained below.
Additional permission granularity can be obtained with the use of other modules as defined in the Extend To Do List.
The permission functions properly, no issue in that regard. However, the name of the permissions should be using "to_do" with an underscore to be 100% compatible