Access control

This module was created in response to http://groups.drupal.org/node/3720 and to simulate sealed comments similar to the whisper function at Vanilla and private comments on blogs at wretch.cc

Its just a simple module for sealed comments, so it does not have any of the fancy features proposed in the above discussion.

Guestbook module support now available! Please install guestbook first before enabling this module or you have to run the 6110 update to have the guestbook table altered.

This module allows users to log into your site securely without usernames and passwords. It uses digital/identity certificates users have imported into their browsers as part of a public key infrastructure (PKI). The certificates can be generated by Drupal's PKI Registration Authority module or any other registration authority (RA) / certification authority (CA).

When a Drupal page is accessed via HTTPS the module checks for certain environmental variables that contain the user's unique information, such as an email address. Depending on the settings it then logs the user in or, if enabled, creates a new account.

This is a collection of modules that make use of User Points module API.

This module provides fine-grained access to projects and issues created with the Project and Project Issue Tracking modules. Where the original modules only provided access by role, this module allows you to specify view, edit, and delete access per user. The permissions are also assigned immediately, instead of requiring the administrator to then go and save the node first. Permissions set at the project level are also applied to the issues for that project.

This module is used to delete all content and/or users from a site. This is mainly a developer tool, which can come in handy in several cases, listed below.

The usual way to do this is to go to Administer -> Content then select all the nodes and delete them. This works if you have a handful of nodes only. If you have hundreds or thousands of nodes, then it is not a practical solution.

Another option is to directly delete the nodes from the node table in the database. This does not work properly, since there are also comments, and many tables for add on modules that needs to be cleaned.

• This is a test site that the client was using for a period of time, and they must clean it up before starting with real data.
• You are testing something that creates a lot of nodes (e.g. aggregator), and want to do it over and over again.
• You created a site in the past and want to replicate it again, but with new content.

Note that for nodes, comments and all additions to nodes that contributed modules may have added. For users, any additional module data will also be deleted.

Usage

Drush

drush delete-all
Example: drush delete-all article

Drush on Drupal 7 version


Delete all nodes, nodes of a specific content type or users.

Examples:

Provides user authentication with Shibboleth (both v1.3 and v2.0) as well as some authorisation features (automatic role assignment based on Shibboleth attributes).