Administration

Allows the use of client-side editors to edit content. It simplifies the installation and integration of the editor of your choice. This module replaces all other editor integration modules. No other Drupal module is required.

Enables styles/templates editing and the creation of new Smarty themes. Works with Smarty Engine only and requires applying the patches that ships with the module.

It is still a work in progress. So use with caution.

Development sponsored by CivicSpace Labs.

Edit term provides links on taxonomy listing pages to directly edit taxonomy terms.

This makes it easier to immediately edit term name, synonyms, description, and weight for the term you are viewing without navigating through your site's administrative back end.

On the term edit page, you also have the new ability to set an URL-alias for the term directly, and create and position a menu item - the same way as can be done for nodes. See illustration.

Once changes are made, you are returned to the listing page from which you started, cutting normal term management procedure down from a dozen clicks to just two.

Visitors find your site with a search engine. Are you interested in what they were searching for?

Search Engine Referers is a simple module to view the search engine queries used by your visitors. It parses the referer URLs of popular search engines in you access log and extracts the search queries. Currently supported: Google, Yahoo!, Live.com, Yandex.ru, Rambler.ru.

Drupal SEO Checklist - What is it?

The Drupal SEO Checklist uses best practices to check your website for proper search engine optimization. It eliminates guesswork by creating a functional to-do list of modules and tasks that remain. Updated regularly with the latest techniques, it makes on-page Drupal search engine optimization hassle-free.

Drupal 8 Note: A ground-up rewrite is currently underway. Follow the progress at https://www.drupal.org/node/2607038#comment-10638286

Back up and restore your Drupal MySQL database, code, and files or migrate a site between environments. Backup and Migrate supports gzip, bzip and zip compression as well as automatic scheduled backups.

With Backup and Migrate you can dump some or all of your database tables to a file download or save to a file on the server or offsite, and to restore from an uploaded or previously saved database dump. You can choose which tables and what data to backup and cache data is excluded by default.

Node Hierarchy allows nodes to be children of other nodes creating a tree-like hierarchy of content. The module offers:

• 1-Click creation of hierarchical menus
• Hierarchical breadcrumbs
• Automatic hierarchical urls using Pathauto (and token module)
  (eg: q=aboutus/history/beginning).
• Automatic creation of hierarchical menus if desired.
• Optional Views integration.
• Optional Node Access integration.

This module makes the q=admin/user/access ("Access control") page easier to use by sorting the permission table so that rows belonging to a certain content-type are grouped together.

Expires rows from the session table older than a certain time.

Background

By default, Drupal ships with a session expiration time of just over 23 days, using this directive in settings.php:

ini_set('session.cookie_lifetime',  2000000);

However, for this to work automatically, it requires PHP's garbage collection to be configured correctly.

Since some distributions, e.g. Debian and Ubuntu do not ship with PHP defaults that triggers PHP garbage collection, there is a need to also set the following:

ini_set('session.gc_probability', 1);
ini_set('session.gc_divisor', 100);

This will work, but has some drawbacks:

• It will be triggered at some random time, rather than at a predictable time.
• It could slow the response for the unlucky user who happens to trigger it.

So, on sites with a distribution that is not setup as above, or on really busy sites, the sessions table can grow to be very large, and that can cause slow accesses to it, as well as slow writes due to locking, leading to performance bottlenecks.

Journal module adds additional fields to all forms in a Drupal site to allow developers and site administrators to record and track all changes that have been performed to setup a site or alter its configuration. Journal also allows developers to maintain a log of applied patches and customizations on a Drupal site, including links to issue trackers like Drupal.org issue queues (starting from 6.x-1.3 / 5.x-1.5).

Journal is primarily useful for developers and site administrators working in a team environment. Since Drupal is a fully-fledged content management framework, it is often not easy to communicate, track and audit all changes that have been applied to a site. Even without contributed modules one is able to build a totally customized site.

Maintaining a log of patches and customizations helps in determining whether a module can be safely updated, and moreover in building sustainable, well-documented Drupal sites.

Journal's log is comparable to the watchdog log in Drupal core. However, watchdog logs can be truncated or emptied at any time, so one would loose all entries.