This module provides an easy way to indicate which menu item is active adding the active CSS class depending the path that the users are seeing.
IMPORTANT
This assumes they are using theme('menu_link') for the menu rendering to html.
FEATURES
The module was built in-house by Development Gateway in order to ease deployment for the Drupal platform. It is used for continuous integration development / micro-release, in order to propagate features and database changes from the development machine to staging/production and also to the other developers.
Provides server/client communication over XML-RPC. See #1033818: Move xmlrpc includes into xmlrpc.module.
This repo has moved, it is now hosted on github:
This module is pretty simple by nature and is very similar to the core syslog module (in fact the vast majority of its code is copied directly from the core syslog module).
The only difference is that it was written to use syslog-ng instead of syslogd or rsyslog.
Tutorial of how to use this API to build a region
Regions in Drupal are defined by the theme layer. This is problematic in instances where you want to add blocks / boxes to a specific region that is theme independent. Some examples of when you would want to use this module:
test menu
NOTE: Untested, has no tests, and is generally untested without any tests. :-)
Fills some of the gaps in Drupal 7's entity CRUD implementation. Turns DrupalDefaultEntityController into a much better factory for entities. Exposes create, save/update, and delete, and lets you define your own hook API.
A simple module that allows you to disable Javascript and CSS aggregation on specific modules, themes, /misc and libraries. This module is intended for sites in development, especially when dealing with IE file limitations and shouldn't be used on a production site.
