Compusure Drupal development

The editing form of a node is themed using theme('node_form'), which is implemented by the theme_node_form() function in Drupal core's node module and can be overridden by adding a <theme_name>_node_form() function in the theme's template.php file. However, this is less convenient and less powerful than taking advantage of Drupal's templating system. Why not be able to override by placing a node-form.tpl.php file in the theme's folder and allow modules to use preprocess functions for customization? This module allows exactly that.

This is a simple module that adds a "node-content" theme hook to Drupal for theming the $node->content array. For example, with this module enabled, you can create a "node-content--page.tpl.php" file in your theme's folder, giving you templating control of the "Page" content type. This can be used for any content type, but the use-case I expect it to be most useful for is in having greater theming control of content types that use CCK fields.
There's another module, contemplate, that solves a similar use-case. That module, however, is more geared to providing template control via the CMS interface, whereas this module is more geared to providing it via the normal theming system. Pick the one appropriate to the way you like to work, or mix and match.

The order of preprocess functions documented on http://drupal.org/node/223430 is not the order actually called by Drupal when a module defines a themehook as having an 'original hook'. This will hopefully be fixed in a future release of Drupal, but until then, this module fixes it.

Without this module, if during the processing of an AHAH callback, css files are added using drupal_add_css() but those files aren't already loaded on the base page from which the AHAH request originated, then those files don't get loaded. This is an unfortunate limitation of Drupal's AHAH system. This module addresses that limitation. However, to take advantage of this, a module implementing an AHAH callback needs to send the response through theme('ahah_response') as provided by the ahah_response module.
If you're interested in this module, you may also be interested in the ahah_script_ensurer module.
This module depends on:
ahah_response
ahah_page_storage
jquery_aop

Without this module, if during the processing of an AHAH callback, javascript files are added using drupal_add_js() but those files aren't already loaded on the base page from which the AHAH request originated, then those files don't get loaded. This is an unfortunate limitation of Drupal's AHAH system. This module addresses that limitation. However, to take advantage of this, a module implementing an AHAH callback needs to send the response through theme('ahah_response') as provided by the ahah_response module.
If you're interested in this module, you may also be interested in the ahah_style_ensurer module.
This module depends on:
ahah_response
ahah_page_storage
jquery_aop

This module provides a way for modules to store information about the state of a page as it changes during AHAH callbacks. It provides no end-user functionality, but gives an API for other modules to use. Examples of modules using this are ahah_script_ensurer and ahah_style_ensurer.

This module provides a 'ahah_response' themehook. I'd like to encourage module developers that implement an AHAH callback to consider using this theme function rather than calling drupal_json directly. Doing so would enable other modules to adjust the response via hook_preprocess_ahah_response.

The 6.x-1.1-dev version of the TinyMCE module doesn't work when used in a CCK text field set to "unlimited" for two reasons. One is that drag and drop functionality provided by Drupal core's tabledrag.js causes the tinymce editor's iframe to be reloaded, resulting in it breaking. This module addresses that problem by altering the tabledrag behavior. While a CCK multiple text field is the most common use-case, this module also enables tinymce to be used in other scenarios that use tabledrag.
The other reason tinymce doesn't work well in a multiple CCK text field is due to integration problems with AHAH. This problem is addressed in a separate module: tinymce_ahah.
This module depends on both the tinymce module and the jquery_aop module.

The 6.x-1.1-dev version of the TinyMCE module doesn't work when used in a CCK text field set to "unlimited" for two reasons. One is that the "Add another item" button uses AHAH and the tinymce module doesn't handle that well. This module enables the tinymce module to play well with AHAH. While the most common AHAH use-case for it is within a CCK field set to "unlimited", this module also enables tinymce usage in other AHAH scenarios.
The other reason tinymce doesn't work well in a multiple CCK text field is due to integration problems with drag and drop. This problem is addressed in a separate module: tinymce_dragdrop.
This module depends on both the tinymce module and the jquery_form_update module.

Similar in spirit to the theme registry, this module allows core and module javascript files to be overridden by being placed in an alternate location.
The logic is as follows:
1. A module can override a javascript file from drupal's core "misc" folder by placing a file of the same name in the module's "misc" folder. If a module is taking advantage of this, it should list the jsregistry module as one of its dependencies.
2. Files in "sites/<site>/misc" and "sites/all/misc" override files in the module's "misc" and drupal core's "misc" folders.
3. Files in "sites/<site>/misc/module_override/<module_name>" and "sites/all/misc/module_override/<module_name>" override javascript files in a module's folder.
The above is the default logic. This module also invokes hook_js_registry_alter(), so other modules can adjust the registry to something else.
This module depends on the jsalter module.