Obsolete

*** Update ***: This project has been commited to drush HEAD, and will be a part of drush4: http://drupal.org/node/663322#comment-3129932

As such, there is no supported release of this project, and it may be considered deprecated. If you need drush_user for drush3, you may download and apply this patch: http://drupal.org/files/issues/user.drush_.inc__8.patch

Original Description:

Namespace for cache. Namespice implements simple API containing wrapper functions for cache management using concept of tags.
Supported cache backend: Memcached (both Memcache API and Cacherouter-Memcache should work).
This is an API module for developers, it doesn't have any usage on it's own. Install it only when required by other module.

State of this module

Namespice is experimental. It's features and ideas will likely be incorporated into some cache backend project, to fully support cache lifetime, stampede protection etc.

Features

• Tagging of cache entries.
• Optimized serial storage
• Atomic serial operations. Multiple thread friendly

Important!

The drush_git module is officially depreciated. No work will be done on this project in the future. Now that Drupal.org uses Git, Drush works with Git automatically. Even submodules are supported in a limited fashion. I expect any further integration to happen in Drush's package manager. In short, don't use this.

What is it?

The drush_git module currently provides a Git core API layer for Drush modules that use Git functionality and some Git deployment commands we are developing for our own organizational deployment needs, that utilize Git submodules. I am thinking that the Git deployment commands will probably get separated in the future into a drush_git_deploy? (not sure on the name) module. So basically there would be a Git API module with no Drush commands, and the Git deployment module that used the API module.

This module allows associating certain ecommerce products with the Licensing module.

At the moment, the workflow is very basic.

Feeds Wesabe Parser enables the Feeds module to import data from the Wesabe API, thereby allowing easy automatic importing of transaction data from a multitude of financial institutions.

This module could be used in conjunction with Views and Views Calc to quickly put together a simple accounting system.

This module makes it possible to display search results via AJAX.

If installed the module can use the Search Lucene API so you can search with wildcards / part of strings. Apache Solr is planned to be added as well.

I'm also planning to convert this module for use with Drupal 7.

The idea for this module was hatched here: http://drupal.org/node/674002

This modules ties author user roles to content, so that the content tied to that role is only publicly accessible if the author of that content has the specified role.

Example use:
User subscribes, get's subscriber role. The subscriber role is tied to 'company listing' content. The subscriber posts company listings and later cancels his subscription which removes his subscriber role. This module makes that content no longer visible.

Want to amaze your friends?
Sick of logging into drupal the "old fashioned" way?
Think that RFID access would be cool?

Then this module is for you!

To login to drupal, simply swipe the RFID tag and a browser will be started (if required) and logged in instantly as your user.

This module was built to enable instant login for Point of Sale with the ERP module by StratosERP.

The rfid_login module utilises services and a user login for security, whilst still enabling amazing convenience.

Turned into a related API module that is more flexible. See: Node Reference Highlight

Initial module code lost before it was committed.