Drupal

Please rate and vote for my “I’m coming to DrupalCon Paris video avalanche” response. A free Drupalcon Paris ticket means more beer money. Daddy needs beer! So give me some lovin’, Drupal community!

Did I mention I rap about Drupal in the video? So go watch the “John Albin Wilkins” one and vote for me! :-D (See the detailed voting instructions below.)

Also, I’m behind in the polls right now! Help!

Ok, I mentioned this in twitter a few weeks ago, I created an issue about it in D7’s issue queue, and there are 2 small print notes in the D6 theme guide, but I don’t think my message was visible enough. So let me just say for the record (again)…

Never, never, ever, ever use phptemplate_ as the prefix for your theme’s preprocess functions. Don’t do it! phptemplate_ prefix should talk to the hand! Expunge it from your memory. It’s an ex-prefix. Seriously, cut it out! So, let me re-phrase:

Every time you use phptemplate_ prefix,
God adds a pointless issue to Drupal’s issue queue.
Please, think of the issue queue!

A few days ago, Jeff Burns wrote “Source Order: why I think Zen gets this wrong”.

His basic premise is that content-first HTML source ordering is an SEO-driven idea, is not backed by any accessibility studies, and goes against user expectations. While I respect his opinions, um… he’s wrong. :-)

Over at Brainnovate, Scott Miller writes that a CMS is bad for innovation. Now his opinion is clearly biased and ignorant of how innovation actually occurs, but there are some points I would like to clear up…

“Just because I haven’t personally used it, I do know a thing or two about Drupal. It *is* a powerful piece of software.”

The swing…

“However, at the end of the day it is still a CMS, not a framework […] in its own right.”

…and a miss! Actually Drupal is much more powerful than Scott knows. Because it’s both a CMS and a framework with an extensive API.

Here’s a quick one if you are in need of a noon-time distraction. If you’ve ever used the WYSIWYG editor TinyMCE, called “tiny mice” by some, then you know that it likes to hook() up with every <textarea> that it sees.

The results of this promiscuity range from annoying (I don’t need a HTML editor for a log message!) to the disastrous (?*$! That HTML editor just stripped the newlines from my list of pages in “Page specific visibility settings!” Oh, the humanity!)

I was just interviewed by Jeff Robbins for Lullabot podcast #55. I’ve listened to this Drupal-lovin’ podcast since its inception, so it was pretty cool to be asked to do an an interview.

We mostly talked about the Zen theme, which I’ve put a lot of work into and, if you don’t already know, is a fantastic foundation from which to build your own custom-designed Drupal theme.

After a month and a half beta period with only 5 bugs discovered (and squashed), the O-fficial Zen 5.x-1.0 version has been released. Yay!

Thanks to everyone who helped with new features, bug fixes and documentation suggestions! The help is greatly appreciated!

Back at the beginning of February, chx (a Drupal master coder) posted a story to Drupal’s homepage asking for people to come together and work on an “elusive login issue” that people had been reporting for over a year. Some users were reporting that no matter how many times they tried to login to Drupal, they would be promptly put back in front of the login form without the anticipated “Unrecognized username or password” error message.

Steven Wittens was a co-creator of Drupal’s beautiful default theme, Garland. And he has a thought-provoking post about the current state of design in the Drupal community and his frustrations in trying to improve it.

Drupal 4.7.4 has a bug in it regarding story previews. The teaser preferences allowed you to set the maximum length of a teaser, but the underlying code treated it as the minimum length of a teaser.

So, say you wanted a teaser that was 400 characters or less; what you would get was a teaser that was always 400 character or more. Ouch.