Actively maintained

Sudo module allows administrators to use the site primarily as a normal user but add permissions to their account as needed for the performance of administrative tasks. Unlike the many excellent user-switching modules often bent to this use (masquerade, impersonate user, devel's switch user), Sudo toggles a configurable set of permissions on the current user's account. This is useful not only for testing a site but also on production sites, in cases when it is desirable for administrators to use the site both as a normal user and as an administrator and yet all activity must come from the same account.

Caveats

Sudo functions by removing and adding user roles on the fly. Any functionality
that relies upon user roles will be affected if those roles are sudo roles for
any users; for example, an action that sends emails to all users with the
"administrator" role will fail if the administrator role is a sudo role for some
accounts that are not sudoing when the action is triggered. To get around this,
you may wish to add a role with no permissions for administrators, and key tasks
that would normally target the "administrator" role to that role instead.

This module provides a user interface to the Grammar Parser library. It allows you to specify individual source code files or entire directories of source code files to be parsed. In addition, source code may be entered directly in a text box. The output file options include the parser tokens, grammar structure, and the rewritten source file.

This module includes automated tests for itself as well as the Grammar Parser library.

The 7.x branch requires:

• the Grammar Parser (as a library, not "enabled" as a module)
• the Grammar Parser Library
• the Libraries API (2.x-dev)

A Drush Make file is also included that will download the Grammar Parser Library dependency. (A Make file in the latter will download both the Libraries API and the Grammar Parser dependencies).

This project is sponsored by Boombatower Development.

Looking for 6.x support?

PIRETS is a module for Drupal which connects to real estate listing (MLS) providers using the RETS (Real Estate Transaction Standard) protocol and impo

This module implements Finnish Checkout.fi payment gateway as an Ubercart payment

File logger is a lightweight module that allows developers to configure a log file from within Drupal and dump variables to it from within a running Drupal app. Its primary function is to support debugging, and it avoids the awkwardness of dumping variables either to the console or to the watchdog table. Instead, using the unix tail command, a developer can easily view debugging output. This is particularly useful when dumping large data structures such as nodes, views, menus, etc.

Installation

• Copy the module's directory to your modules directory and activate the module.
• In Site configuration > File logging (admin/settings/flog on D6 or admin/config/development/flog on D7), specify the path
  to the log file(s) and the default log file name.
• (Optionally) Configure the date string to be included with each logged variable.
• Ensure that the user running the webserver has write permission on the file you specify.
  It may be simpler to create that file in advance using the unix command 'touch' as in
  'touch /var/log/drupal.log'. Then, set the permissions on the log file so it is writeable
  by the web server user, e.g. 'chmod 777 /var/log/drupal.log'.
• Enable file logging. When disabled, no output is written. You'll probably want to disable
  file logging in a production environment.

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.