Still on Drupal 7? Security support for Drupal 7 ended on 5 January 2025. Please visit our Drupal 7 End of Life resources page to review all of your options.
Need to add a list of admin OpenIDs to many websites and not lose sanity while maintaining that list across all servers? This module is for you.
You can still maintain arbitrary list of OpenIDs on each site, but the framework ensures a list of allowed and banned OpenIDs (for the "admin" user), in addition to the local list.
This tool is for Drupal service-providers that maintain many websites and need to give admin access to a number of people, across multiple websites, for maintenance and support purposes.
Download YAML library from: http://code.google.com/p/spyc/
Extract zip file and install spyc.php under "spyc" sub-folder of sites/all/libraries (or sites/sitename/libraries).
Also, please make sure to read README.txt accompanying the module, for installation and configuration instructions.
Maturity Status
Both client and server modules of the framework have been thoroughly tested in development and have no known issues. However, these modules are new, and have been used in production, only for a limited duration.
This module is here to alleviate frustration when trying to manage permissions in Drupal. By providing a better permissions interface hopefully a few innocent keyboards and mice can be saved.
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.
Enhancing "modules installation" page by adding "install via ajax" button. When you click this button - modules will be installed in a simple, nice way without page refreshing.
New module that provides a UI for altering forms. This module will also support export/import operations and generating module code for a static hook_form_alter module.