Module weights sometimes come into play when you're trying to override certain aspects of the core or other modules. If you look in the Drupal database's system table you'll notice a field called weight - this is what determines the order in which all of the installed modules' hooks will get called during a page request.

The initial release of the Bones Module for Drupal 6 is now available at http://drupal.org/project/bones. Functionally it is more or less identical to the original Drupal 5 release, with updates to the internal Menu API code.

The Bones Module facilitates rapid site wireframing by importing YAML outlnes.

A technique that I’m finding quite useful during module development is to create a “stub” function for use as a generic interface callback for menu items that I want to define, but haven’t yet written callbacks for. For example, if I were building a Drupal 5 module called widgetmaster, I would define:

I just encountered a problem arising from a combination of the TinyMCE WYSIWYG module and the FAQ module in Drupal 6.

In a nutshell:

When I first started using Drupal a year and a half ago one of the first things that struck me about building out sites (that is, sites consisting primarily of Primary Links pointing at Page nodes) was that it building out a skeletal wireframe of a site gets tedious, especially if you have a lot of "static" pages; we're all familiar with the drill: