Developer

Editarea provides replacement of plain text boxes with the EditArea javascript code editor, making the editing of code directly in a web browser much more reasonable.

In addition to text box replacement, this module provides a script for creating a "Drupal PHP" syntax-highlighting file from your local Drupal installation.

This module integrates the YUI Logger into Drupal .

NOTE: This module depends on the YUI module. You need to install the YUI module for the logger to work.

Videos

COMING SOON

YUI Dependency Issue


Both releases now require YUI 2.5.1. Sorry for any inconvenience. We are working on coming up with a dependency solution that is less abrupt.

Codemetrics provides static code analysis and software metrics for PHP projects and Drupal codebases in particular.

To see this in action, check out the Broccoli project.

This is pretty much alpha code - it's still fairly experimental. Expect APIs to change without notice.

This module is no longer in use, and is likely not going to be updated. The documentation below is for historical purposes only.

This is the basic module we use on all our client sites. Feel free to use it on your sites too, however, be warned that it's written specific for our client setup.

It adds a line to admin/logs/status to show the svn tag and revision number.

!NEW Release 2.2 is finally out, with code & performance improvements and a lot of new features! Check changes in release notes

Elysia Cron extends Drupal standard cron, allowing a fine grain control over each task and several ways to add custom cron jobs to your site.

• Set the timings and frequencies of each cron task (you can run some jobs every day at a specified hour, other only monthly and so on...). For each task you can simply choose between some frequently used options ("once a day", "once a month" ...), or use a powerful "linux crontab"-like syntax to set the accurate timings. You can even define your frequently used options to speed up site configuration.
• Parallel execution of cron task: you can group jobs in channels and execute then simultaneously: so a task that takes a lot of time to execute won't block other tasks that need to be executed every 5 minutes...
• You can disable all tasks, an entire channel or a single task.
• Change the priority/order of task execution.
• Manual force the execution of a cron tasks.
• Detailed overview of cron status with time statistics for single tasks and channels.
• powerful API for module developers: you can define extra cron tasks for your modules, each one with own default timings (site administrators can override them by configuration, other modules via hook_alter).
• Administrators can define custom jobs (call to functions with parameters), via the "script" option.
• Several optimization for frequent cron calls and error handling.
• Protection from external cron calling by cron_key or allowed host list.

Elysia has no dependencies with contributed modules, and doesn't need to patch the core: it can be used in minimal Drupal installation with only core modules.

3rd party integration:

• Ping feature, for external tracking services like host-tracker to tell whether cron is functioning properly on your site.
• Drush support: you can call "drush elysia-cron run" to manually run extended cron.
• CTools support for exports/backup of task settings.
• Features support.

This module provides additional API functionality to other modules. You do not need this module unless you are instructed to by other modules to add it. Module developers, to use simply call modver::module("module_name") to get an array of the version for the module. The array[0] is the major version for the module_name given. If the module is not installed then FALSE is returned. Theme developers can use modver::theme("theme_name") to get the version of a theme.

The views modify query creates a views filter that lets you run PHP code to modify the query when it is build. In addition, it provides a Views field that lets you display any output generated by the code in the filter. This can be very useful when developing sites.

This is a module for advanced developers only ; only use it if you know what you are doing and understand the Views API.

Using this module can cause data loss. Only use it on development sites, and only if you know what you are doing

This module allows you to determine code coverage using the xdebug code coverage framework.

Installation

Due to the low-level entry point of code coverage the patch is hard-coded to point to sites/all/modules/code_coverage. The code_coverage module must be placed there in order to work unless you alter the patch accordingly.

About

Config to Code module for Drupal 5 makes it easy to deploy new views and panels and to version-control changes to existing ones with a source code repository like subversion. It makes it quick and easy to move configured views and panels in the database to code, then safely delete the configured views from the database and finally, expose the views and panels in code back to their respective modules. It is extensible for other types of configurations that can be stored both in database and code.

The stage module taps into Drupal's revision system to allow host-based staging of content stored in the database. For content types specified in the admin section, new content or edits to content are stored as revisions, but the node itself retains its current revision until an administrator pushes the content (also in the admin section). A set of changes between pushes is grouped and pushed all at once, and the change set is named upon push. The list of revisions associated with a given change set can be viewed both before and after a push.