Actively maintained

Drupal 7 has a new and efficient way of loading module and theme settings from the database. The new loader requires all settings to be stored in the current (serialized) format.

An unfortunate side effect is that any left-over settings from modules that did not clean up when they were uninstalled, and are not stored in the correct format, cause PHP notices on your site.

This may happen if you've for instance upgraded a site from Drupal 5, through Drupal 6 to Drupal 7.

This module lists all entries in the {variable} table that cause unwanted PHP notices on production sites, such as:

Notice: unserialize() [function.unserialize]: Error at offset 74 of 75 bytes in variable_initialize() (line 749 of /srv/www/<sitename>/includes/bootstrap.inc).

By knowing the offending variable name, you can remove it from the database, making the notice go away. Of course, you should probably notify the module or theme author that their module or theme does not properly clean up after itself.

If you find a variable that causes a problem, please note it in a comment on #1284364: Use variable_initialize() against broken values - Notice: unserialize() [function.unserialize]: .

Related Modules

• Variable Cleanup — Checks for unused variables in your variable table by scanning your entire filesystem for unused variables.
  

This module modifies the default "taxonomy_term" view provided by the Views module to provide multi-term node display functionality.

This module provides more features for developers and themers when they debugging drupal.

On 404 Not Found error pages, Drupal will skip rendering of all the navigation links of your website for performance reasons*. Some of these include:

1. The "Primary links" block and any other menu links block.
2. The Primary links and Secondary links of your theme.

* Unless you have configured a "Default 404 (not found) page" on admin/config/system/site-information.

But many websites find navigation invaluable. Especially on 404 pages, when they want to show lost users how to get to real pages.

So this module simply revives those features on 404 pages. Simply install and enable the module. No configuration needed.

Easy Authcache is module that makes authcache implementation easy,faster and makes it comportable with drupal community modules.

Created & developped by ADYAX

Advantages of module differs it from Authcache:

1. It makes unnessary for developer to write client side callbacks for authcache module (js functions).
2. Makes server side callback as hook (drupal style).
3. Includes all modules.
4. Handle js files and settings, needed for retrived with ajax html, on final page.
5. Handle url context dependent code.
6. Provide api to handle theme functions, you need, with authcache.

Disadvantages of module differs it from Authcache:

1. Makes bootstrap FULL on authcache ajax callback. That can make slowly then authcache manual implementation.
2. Can lose some js Drupal.settings after authcache ajax result.
3. Higher, then for manual authcache implementation can be, load on client side (js code).

Installation

To install Easy authcache

• Install required modules (common way - Authcache)
• Add Easy authcache module drupal contrib modules dir (usual /sites/all/modules).
• Copy authcache_custom.php file from easy_authcache/_authcache/authcache_custom.php to authcache/ajax/ and change (authcache/ajax/authcache.php:str 42) to include authcache_custom.php, if needed.