Unsupported

The Mover modules provide the ability to move content between Drupal sites. Out of the box this module supports nodes, users, taxonomy terms, URL aliases, and path redirects. The module currently supports D6 to D6 and D6 to D7. Drupal 7 exporting (for D7 to D7 migrations between different site builds) will be coming next.

This module has similarities to other migration modules, and is most similar to Node export which was the foundation for it's creation, but this module is significantly different than others. One major difference from Node export is that this module writes to separate text files for each piece of content, which is better for PHP memory usage during a batch import. Another difference is that Node export doesn't migrate users.

Compared to other migration modules a big difference is that the Mover module UI is only used for running processes, not for configuring or mapping data. All data mapping is done with custom modules that implement the appropriate hooks. The advantage is that programmers who learn the API can very quickly write complex migration scripts. No UI can account for all the possible options needed for a complex migration.

Address classifier of Russia (KLADR)

This module creates a tables:
- kladr
- street
Imports data into them.
Supports the relevance of the data.

User Status provides a block that shows other users' status, such as Away, Out to Lunch, Out of Office, etc. Also gives you the option of adding your own comment.

Allows administrators to destroy all nodes and users associated with a domain when the domain is deleted (via Domain Access).

Now that the API requires OAuth to authenticate and retrieve feeds, this module will not function properly and should not be used.

Twitternode creates nodes from a Twitter feed. Nodes created by Twitternode are standard Drupal nodes, and thus can be extended by CCK, included in Views, etc. This differs from some of the other Twitter integration modules that exist, which store their Twitter data separately from nodes, or pull them on demand from Twitter.

Twitternode attempts to play nice with the Twitter API and only requests the most recent status updates. It downloads new content from the feed each time cron runs. Also, because it keeps the updates as nodes, it effectively functions as a local cache of that Twitter account.

Some potential uses of Twitternode include:

• Implementing a "news feed" that aggregates several different services' feeds, including Twitter.
• Keeping a local backup or mirror of a corporate Twitter feed.
• Seamlessly integrating your Twitter feed with your site's other node-based features.

There are options for how to handle the node title field, '@' replies, and taxonomy.

Future development

I will not be developing this module further.

Form Clerk is an administrative utility that provides a semi-automated way to input data into a Drupal form. Multiple instances of form data can be entered with one command.