Actively maintained

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:

This is a prediction market (AKA event derivative or idea future) module for Drupal. The goal is to provide a free, open source, prediction market tool enabling anyone to build their own prediction markets for education, entertainment, profit, or all of the above.

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

This module implements a revision system for comments. Features include:

About Basic webmail

The Basic webmail module allows one to read and write e-mail through an IMAP mail server. There are not a lot of fancy features (thus the name), just a usable webmail client.

#D7CX: Drupal 7 stable release status

Here's what the current plan is:

• For 7.x-1.x, I'm just going to do a straight update from D6 to D7. This is in process but is currently available only as a development version.
• After that's done (or close to done), I'm going to create a new 7.x-2.x branch and start the refactor process there. It won't be a total rewrite, I'm just going to restructure some things and change to using other modules where it makes sense to (like using Views for the mail list). (I've actually started some of this in the 1.x branch, due to the size and complexity of the module. The additional features, like Views integration, will still not happen until 2.x.)
• After that's done and fairly stable, I'm going to create a new 7.x-3.x branch to start implementing some new functionality that I've had in my mind to create.

Update (2013-04-16): the above plan is still valid. However, I did more refactoring in the 1.x branch than I originally planned, so the 2.x branch may not be as drastic of a change as I had imagined.

Security Concerns