Administration tools

Drupal allows you to define a different theme for administration pages (Administer -> Site configuration -> Administration theme). By default this only applies to pages with a path starting with 'admin' and content editing pages.

The Administration theme module allows you to use this theme on more pages like :
- batch processing pages
- devel node load and render pages
- coder code review pages
- pages you define yourself in the provided textarea

Some of these options will only be available to you if they apply to your installation, i.e. you have the module installed which generates these pages.

Use default theme (not administration theme) for anonymous users on admin/*

This is possible using this module. See issue http://drupal.org/node/372156 for more details.

Module maintainers

You can add extra pages by implementing hook_admin_theme_options in a module.
For Drupal 7 the hooks are hook_admin_theme_info and hook_admin_theme_check

How can you get involved?

• Help write or improve the documentation.

Improves the Input Formats administration page. Makes it less painful to manage, configure and test these sometimes tricky groups of input filters.

The Authoring Aliases module changes real author of nodes or comments uppont it's submission.

For example, it usefull when you don't want to show identity of your root user.

The Roboconf Module is a development tool which stores presets of block configurations and site/theme settings, permissions, etc., allowing a theme developer to easily switch between preset configu

This module shows how modules can be enhanced by or enhance other modules by using information provided in module .info files (implementation of #328932: Modules and partial dependencies - enhances[] and enhancedby[] field in modules' .info.yml files).

The following are all the supported directives:

dependencies[] = modulename
recommends[] = modulename
suggests[] = modulename
enhances[] = modulename
breaks[] = modulename
conflicts[] = modulename
replaces[] = modulename
supports[] = modulename

This information will most likely be used on the redesigned drupal.org, so start implementing this now in your own modules!

At Tribute Media we have many sites in various stages of development. Sometimes upon returning to them I have noticed that Update Status has not checked for updates for up to 4 weeks. I then notice that the "drupal_http_request_fails" flag is set.

It is my understanding that when the variable "drupal_http_request_fails" is set the only way to get Drupal to re-attempt to make a request if to manually reset the variable. Drupal doesn't even check anymore until I reset the flag.

This module allows the user to configure when to check if the flag is set, and reset the flag. The interval is configurable from 1 minute to days or weeks.

When the interval times out the module checks "drupal_http_request_fails" to see if it is set to TRUE - meaning that no HTTP requests are being attempted - this module will reset the flag and log to the watchdog table. If the variable is set to FALSE - meaning that there is no problems making HTTP requests - it logs this to the watchdog table as well.