Heine

Six tips for getting help with your code, because efficient use of volunteer time is key in getting good and timely support. While this is somewhat geared towards Drupal support on the Drupal.org forum and in the #drupal IRC channel, the tips apply to nearly all code you need help with.

1. Post code.
2. State the goal and the problem.
3. Post actual code.
4. Make it short, make it matter.
5. Make it complete.
6. Make it readable.

To more efficiently review code changes in Drupal I've decided to write a little bot that regularly reads the RSS feed of Drupal core commits. It then downloads the referenced patches and creates new content on this site (example) under the category Drupal Core.

As this is a taxonomy term, it comes with the Drupal benefit (tm) of an RSS feed, I now use to quickly review commits to core.

It was a difficult delivery, but Drupal 5.2 and 4.7.7 have finally been released. As you can read in the release announcement, several vulnerablities were fixed.

There are two advisories:

I've written before about (ab)using %s in IN clauses such as:

Should time permit I hope to work on MyCaptcha 5.2 this weekend.

Planned features:

• Support for recaptcha.
• Configurable location in forms.
• Configurable description on the CAPTCHA.
• A minimal API necessary for recaptcha and to silence the voice in my head screaming for a more flexible API.

I promise MyCaptcha won't be about 'APIs'; I will focus on the "Just Works" principle.

A 1.0 version of the alternative CAPTCHA module, MyCaptcha, has been released for Drupal 5.x.

Features:

• Math CAPTCHA
• Image CAPTCHA
• Can be added to nearly any form, without changing PHP code.

» Download MyCaptcha

For additional information, please see the MyCaptcha manual.