Bevan Rudge JavaScript and web technologist

Drupal's template files (*.tpl.php) are not really templates. This is what my DrupalCon core developer summit submission is about. The slides briefly explain why tpl.phps are not real templates, what real templates are, why this is a problem for the Drupal project and community, and mentions some possible solutions to the problem. It also provides some basic guidelines as a starting point for tpl.php standards, should that be pursued.

I just got this email from Mozilla about the soon release of Firefox 3 release candidate, asking addon developers to get their extensions updated and released for FF3 RCs. If you have an extension released on addons.mozilla.org you would have received this email too. I have two variations of FF2's default Mac theme that enable favicons in the bookmarks toolbar: Mac Favicon and Mac Favicon XL.

Almost a month ago I blogged about how much spam I receive. At that time it was around one spam email per 100 seconds (average over the previous month). Since then I've updated my crude spam rate tracker twice and I'm now receiving approximately one spam every 90 seconds. If you look at the numbers carefully you'll noticed that today's count was less for all mailboxes except one; N L AR, the catch-all address for lucion.com.ar. The spam count for that mailbox increased dramatically from about 1000 to almost 4000. Most interestingly, I received almost 150 automated replies to spam messages from unused @lucion.com.ar addresses:

For those that don't read the development list; there has been considerable discussion recently (following Khaled's PG vs MySQL benchmarks) about improving PG support in drupal 6.

I haven't followed the whole discussion in detail (so please correct my if I'm wrong or have missed something), but it seems that for PG support to be sustained and/or improve in drupal6, more PG testers and developers with an interest in PG support are needed.

Chris Messina's (aka Factory Joe) review of drupal 6 is a big contribution to drupal usability. I have highlighted about 50 actionable issues that have been raised and/or discussed through this review. Most of them are trivial changes for drupal 6, but are key usability improvements. Many are simply improving the help text. Some are larger tasks that require more work and changes and should probably wait for drupal 7.

My largest code contribution to Drupal core just got committed! :) At last node_teaser() can take a rest -- at least for a while anyway. It looks like there'll be another round of work on it for Drupal 7).