Under active development

This module extends the Drupal core variable API that handles persistent variables. It implements a class that:

Just took over the module. Will be making stable releases for Drupal 7 and will support Drupal 6 for major issues.

• allows finding the directory where a library has been installed (branch 2.x for Drupal 6 and 7),
• forces Drupal to re-build the menus (branch 2.x for Drupal 6 and 7),
• allows obtaining the value of a persistent variable without passing the default value to each function call,
• deletes multiple persistent variables,
• and implements functions to centralize static PHP variables. The functions are a back port of drupal_static(), and drupal_static_reset() implemented in Drupal 7.

Installation notes

Install the module only if you are instructed to do so, or you are a developer and want to use the module.

If you are installing Variable API because it is a dependency of another module, you need to first install (and enable) Variable API, and then install (and enable) the other module. If the modules are enabled at the same time, you will get the error message class Vars not found. The same problem is actually present if you install a module that depends from the Variable API using Drush; in the moment I am writing this note, Drush will not download the Variable API module, with the consequence that you will get the error message class Vars not found.

The Mark module allows users to "mark" any kind of content that is accessible to Views. Mark allows content to be "marked" per-user or globally. The module provides blocks to mark (and un-mark) nodes and users as well as a View field that can be used on any type of view. Mark is designed to be used by authenticated users. It's possible to assign the proper permissions for marking content to anonymous users, but the behavior of the module in such circumstances is "unspecified", at best.

Mark depends on three other Drupal modules: Views, Chaos tools and
VotingAPI.

Mark leverages the VotingAPI and Views to allow for many kinds of 'marked content' listings. Mark uses Chaos Tools to provide exportables and Features support.

How is mark different from Flag/Nodequeue?

Mark is, first and foremost, a VotingAPI module. VotingAPI does a the heavy lifting of recording votes, tallying them and providing Views integration.

Mark is Views-centric. Modules don't need to provide both Views integration and Mark integration. If a module provides new "base" tables Mark just works.

This module brings API of Eve Online to drupal and is still in very early stages of development.

Connector makes it easy for other Drupal modules to connect and sign in Drupal users with accounts on other services. Connector takes care of the generic stuff like UI, account creation, storing of metadata like name and avatar etc.

Be sure to download at least one implementation for this module to be useful.

This module depends on the Deploy module and adds the ability to deploy nodes automatically after creating or updating a node without u