If you're one of those SEO obsessed people and if you're also a Drupal user, then you'll probably know about the Meta Tags module (also called Nodewords). You might even know about the Page Title module too. And, just maybe, you've also tried to find a way to change the <title> text, not only on nodes (which Page Title does just fine), but also on taxonomy/term pages (which neither module does at all).

In keeping with the theme of the previous post, here is another fantastic tip for pulling out more levels of your primary links menu.

By default, Drupal gives you primary and secondary links. These can come from the same menu tree; primary links will be the first level, and secondary links will be the second level. But what happens when you want the third level? Drupal does not give you this variable by default.

There are quite a few posts about setting the active trail properly with primary & secondary links. In Drupal 5.x, its actually handled pretty well if you use the following code to print your primary & secondary links in page.tpl.php

After an almost 3 month vacation in the South, I have returned to a cold and snowy Montreal. I was hoping that I had skipped out on the winter weather, but 20cm of snow greeted me on my return and gave me the opportunity to work on shoveling technique. We're rapidly running out of space to put the snow, so spring better get here quickly :)

Seeing as I have a lot of work these days, and clients are always asking me to tweak stuff, I thought it might be a good idea to have some sort of version control on the stylesheets, template files & modules, that I work on. That way, if something I do breaks something else, I'll be able to rollback more easily to a previous working version.

So I set about trying to figure out how to do this on a Windows XP machine using CVSNT and WinCVS. Information is pretty sparse on the ground, especially for CVSNT v2.5.03 - most info is for older versions.

I finally scraped together some time and updated my website to Drupal 5.3. I still had some flexinode content on the site that I have now switched over to CCK nodes. I also changed the Portfolio system so that each project is now a CCK node - I used image module for this before.

I am still planning on updating the theme, so this back-end update was the first step in that process.

Now I am able to use the latest and greatest version of CAPTCHA to block those freaking spammers. Try get through this, you little buggers!

For the Quebec Chronicle-Telegraph website, I was asked to create a system whereby users could sign-up for one of three types of newspaper subscription, and at the same time, get a user account with access to premium content. Each of the three subscriptions would require different information from the user. This requirement precludes the use of the regular core profile module (that module provides one set of profile fields for all roles).

Seems like the Captcha module I had installed wasn't working properly - it always said the answer was wrong. Anyway, I have now removed the module and have installed the Spam module instead. I have used it recently on a few sites and it seems to work well, so we'll see how it goes on this site. Just make sure you don't use the word "cialis" anywhere in your comment, or it will be deleted immediately - no questions asked. Yes, I hate spammers! May the fleas of a thousand camels infest their armpits!

After having struggled with this issue for several days - and finding a solution - I thought I'd share this with you all.

The issue I was having was when an image was inserted into a node, it would be visible while I was logged in. However, anonymous users couldn't see the image, even though the path seemed correct.

I was using img_assist and IMCE to do the insertion and both had the same problem. Hence, not a problem with either of them.