Developer

The purpose of this module is to automate as much as possible the task of updating a contributed module for Drupal API changes, and thereby simplify the task of porting contributed modules shortly after a new Drupal release.

For Drupal 7.x, Deadwood is being merged into the Coder project and renamed to Coder Upgrade. Check out the latest features here.

Starting a module conversion is even easier than before. Convert your 5.x module here without installing Deadwood.

Check out the case study.

The 6.x version of this module helps update the 5.x version of a contributed module to the version 6.x API. Currently, 70 of the 80 topics (which often include multiple items) mentioned in the converting 5.x modules to 6.x roadmap have been addressed. This includes 15 of the 17 Form API topics mentioned in the 5.x to 6.x FormAPI changes roadmap. The module probably handles the bulk of changes in many modules, including the Schema API, Menu API and Form API.

Backup Client-Server is a set of modules that allow for the backup and monitoring of a single or multiple Drupal websites.

We have been fairly busy and have not had the time nor the personal need to upgrade this project to D6. If you are interested in becoming a co-maintainer, please contact us at http://collectivecolors.com

The Active Template module is similar to the ConTemplate module except that it works with Views instead of content types. Essentially it gives you the power to customize your views displays in any way that you can imagine. The Active Template module allows you to:

With Drupal 7 released, Drupal 5 is no longer supported, so this module is officially obsolete. However, if you want to take over its maintenance, please contact me.

This module enables Drupal 5 module and theme developers to use some of the API features available in Drupal 6. Right now, this module implements the drupal_alter function from D6 and the image_button element type from the Forms API. With time, this module can evolve to have more D6 goodies. Please submit issues if you have requests for what you'd like to see.

I have no plans to port this module to Drupal 7, because I don't believe it's useful for D7. D7 core has sufficient hook invocation that most customization use-cases can be solved without hacking core or an established contrib project. For the remaining occurrences where fixing core or a contrib project is needed, it is best to do so with a patch. Also, GIT makes managing patched versions easier. Finally, where OOP in Drupal still makes sense, it is being slowly introduced, such as the D7 database layer.

This module provides integration between CCK fields/widgets and the Forms API. It provides no functionality to end-users, but it enables developers to re-use the functionality provided by CCK field types and widget types in contexts other than what is normally provided by content.module.

I will not be upgrading this module to Drupal 6 because CCK on D6 already takes the approach of encapsulating widgets in form element types, making this module no longer useful.

TBD

This project is out of date, and hasn't kept up with progress in the Services module. Seeking co-maintainers or other contributions.

A set of classes and and tests that Python developers can use as a basis for integration with the Services module.

Currently, features are fairly slim, but more will be added over the coming weeks. Contributions more than welcome!

Documentation

A draft version of the User Documentation is now available for the Custom Page module.

What is it?

Custom Page is an advanced theming tool, allowing developers to easily create pages with custom templates and maintain full control over the output (e.g. HTML). Custompage seamlessly integrates with the Context module (both versions 2 and 3) module and while Context is not required, the two work great in tandem.

This module is supposed to ease life for developers - if you are none of those, you only want to download this module if another one depends on it. So now that that's sorted out, let's get to the point...