The small things that make life easier with Drupal
In the recently introduced Drupal RC2, a pair of new functions have appeared: theme_search_block_form() and theme_search_theme_form(). They replace the ephemeral (some said "Easter Egg") theme_search_box() appeared and disappeared between RC1 and RC2, and raise important issues for themers.
The recent removal of the quasi-official node_validate_title() function from 4.7 causing various errors with contrib modules, I wondered whether there wouldn't be a way to trap such errors in a way that would be helpful to newbies, instead of the current situation where all they get from their newly haphazard drupal install is a PHP fatal error.
The idea, then, is to register obsolete functions in some form of legacy maintenance module, to generate a useful help page pointing the user to a doc page on drupal explaining why there is an error in his configuration and what he should do. In node_validate_title()'s case, the help is a bit succinct: http://drupal.org/node/22218#node_validate_title.
Zend Studio is a convenient environment to code in PHP, which is why many Drupal developers are using it. But some settings are necessary to ease its use, due to the specific extensions Drupal uses.
Ofttimes, when developing a site, you can be led to create or import a large number of custom nodes, for instance flexinodes, only to have to delete them later on. Doing it by hand in admin/content is inconvenient when the number of nodes is large, and for custom nodes like flexinodes, the exact entries to delete in the various Drupal tables may not be obvious. Time for a workaround.
XML-RPC is a very simple RPC service, but it may not be obvious how to provide it from Drupal. Here's how.
Some sites include a list of terms recently searched for. I've created a patch for Drupal adding this functionality to the current 4.6.x search module.
The documentation for hook_user can cause an unforeseen problem...
You're peacefully coding a hook_load implementation in your latest drupal module, when your admin account suddenly gets "Access denied" errors looking at nodes. Yikes...
Sometimes, a double slash appears in your Drupal URLs. This is an error both common and simple to fix. Here's how.
hook_form is used both for adding new nodes and editing existing ones, and no parameter is passed to describe the current operation.
Why is it not needed ? Because a simple test can show whether the node is being added or edited: