Thank you for he nice tutorial. Keep it up man
-Nish

Good call amigo. I guess I'm the first to submit this to Stumble, so expect another hundred uniques a day (I think).

You're welcome.

Heehee Nick, the burden of proof is on YOU. And remember: extraordinary claims demand extraordinary proof ;-)

I'm a 100% total Drupal n00b and a major WordPress user, but I'm failing to see how PHPTemplate is different on a code-level from the WordPress theming system. That is to say; obviously, the way themes are applied to content is different (Drupal's content and publishing model is very different than WP's) and again, obviously, the APIs are distinct. But I'm not, thus far, finding major conceptual differences between WP's "template tags" and inlined PHP logic and PHPTemplate. Does anybody care to enlighten me?

I've been trying to get a question answered over on the Drupal forums (http://drupal.org/node/67684) but since it's a theming question I'm sure you know the anwser and it seems to fit in with your series here. Can taxonomy be used as a variable in template.php to control output such as whether or not an event date is output to the page? For example, if I were to event enable book pages, but I didn't want a date to be associated with particular book pages, at least not when the node is displayed to the person viewing the page. Or is there a cleaner way to handle that than taxonomy and template.php? Roger

You state: So just to review your theme’s files should be: /themes/yourtheme/template.php /themes/yourtheme/user_login.php Shouldn't that be? So just to review your theme’s files should be: /themes/yourtheme/template.php /themes/yourtheme/user_login.tpl.php

Very nice tutorial, Nick! It's very refreshing to see that as your technical knowledge of Drupal has grown, and as you've started to write more "geeky" articles, your writing style has remained friendly and accessible. A noble goal for all of us Drupal bloggers, slash tutorial-writers. This tutorial does a great job of explaining that with the 4.7 forms API, you can override more than just theme_foo() functions in your theme. You can also theme any form, including one that doesn't have a theme_form_foo() function (i.e. you can override the theming of a form, even if there's no default theme function to be overridden for it). This is probably not obvious to many Drupal themers, especially those that are used to the limits of 4.6 theming. However, I have a few suggestions: 1. Themers can also output nodes directly in their theme with a call to node_view($node), or with a call to theme_node($node). This is preferable to directly printing the node title and body, unless you really need the extra flexibility. 2. node_view() wraps the title of the node in a call to check_plain(). So any method that bypasses this function (including calling theme_node(), or printing the title directly), should use check_plain() before printing the node title. Failing to do this will open a potential security hole in your site. 3. I'm not a big fan of hard-coding node IDs, even in a themable function. IMO, themers should instead use variable_get(), even if there's no front-end interface for changing the variable in question (you can at least develop one later if necessary).

+1 on the handbook suggestion. Well done!

Great explanation! very useful! saving as pdf!

This was a really good tutorial. Thanks.

Awesome tutorial! We need more like this :-)

Yeah!!! Great work! Thanks for telling the world about the greatness of PHPtemplate!!!

Bravo. I hope you put this in the drupal.org handbook.