I'm proud to announce that the first DrupalEasy podcast has been released.

Mike, Ryan and myself end up talking about the Drupal Association election, Drupalcon Europe 2009, Drupal + Mobile, Plug in Manager and Fields in core among other things.   I think it's worth a listen even if you aren't a hardcore Drupal person since we try to keep the content at a mid-level but I'm obviously biased.

This entire post came about due to a great screencast by Addison Berry about using secondary menus. If you haven't already seen the screencast or you don't understand how to make the children of the primary navigation show up as the secondary navigation then you must watch the screencast.
I'll come out and say it, before watching this screencast, I didn't even know using the children of the primary navigation as a secondary menu was even possible.  I had always used the secondary navigation for things like footer navigation and created individual menus for the various sections of the site and placed each block.

The other day I heard about Cache Router, a newish module for Drupal that allows multiple ways to cache content in a more scalable manor than the default Drupal caching. Since the Memcache module has been lagging behind for Drupal 6, I decided to give the new module a whirl on Developer Karama (using the Memcache method).

At the last Florida Drupal meeting one of the attendees (sorry, I'm horrible with names) asked why Drupal was so difficult to upgrade.  At first we were a bit confused since we thought Drupal was easy to upgrade but we later found out that the user was storing his modules in /modules and themes in /themes so every time he wiped out his Drupal installation he had to re-install all of the files for his modules/themes.  While it sounds like this is uncommon, I can assure you, it's quite common for new (and some experienced) users to make this mistake.

I just ran across a bug in Drupal that was drastically affecting my XML Sitemap listings.  The bug made it so my blog posts were listed as node/{number} in my sitemap rather than the path auto path.  After much searching it looks like the module weight on XML Sitemap was set to 2 so it was checking the nodes path before path-auto was setting the path alias.

The Google Analytics module for Drupal does exactly what you would expect... it lets you add the Analytics code to your site without having to get dirty in any code!

In addition to standard Google Analytics tracking this module lets you track users by profile fields & file downloads which can be really powerful.

The steps to get Google Analytics working are simple:

Find URL Alias (aka find_path) allows you to search through your sites alias listing (/admin/build/path) using wildcards allowing you to skip scrolling page by page to find the alias you want to edit. That's it, it just adds a search feature to the already existing url alias section.  It won't actually change your aliases, make them faster or solve world hunger but what it does do, it does well.

1. Checks the current URL for an alias and does a 301 redirect to it if it is not being used.
2. Checks the current URL for a trailing slash, removes it if present and repeats check 1 with the new request.

SEO Checklist is a must have Drupal Module for all Drupal sites. It creates a checklist with handy links to the modules/settings that help make your Drupal installation as SEO friendly as possible.
Now I know what you might be saying... "I'm a Drupal expert, I don't need a module to tell me what modules I should be running." Well, I don't believe you. Even the most grizzled developer can forget to add a module or *gasp* not know every Drupal module in existence.