Late last week the Drupal project released a security update and bug fixes to the open source content management system that powers our hosted service and that comes with our VPS package, increasing the version number to 5.11. Today we are releasing a new tag that incorporates this update, which also includes some contributed module bug and security fixes and some new themes. The new tag is 2008-10-15s. You will need to run update.php to clear the menu cache and other caches on your website.

As mentioned, we're taking the opportunity to update some of the modules that come with our supported package. CCK includes a security release of its own, and we've also updated Mollom and the Link module to their latest official releases. In addition, we're adding support for our French install profile, as well as three themes developed by Raincity Studios' very own Hubert Florin. The list of themes and more detailed module release notes with links to the Drupal.org changelogs appear in the release notes for 2008-10-16s.

As usual, we'd like to remind you of our instructions on how to upgrade the VPS installations of Drupal to the latest tag, and to take this opportunity to make backups of your database(s) before upgrading.

As per the security announcement regarding a cross-site scripting vulnerability in the Node Reference module, we've released tag 2007-08-15s. Yes, the lowercase 's' breaks with our previous practice of using uppercase: 'S' looks too much like '5', especially since today's date is the 15th.

We've also updated the Calendar module to 1.5. Note that if you see a "user warning" error that relates to the calendar_ical table missing when running update.php, you can safely disregard that error. See the bug report on Drupal.org and the subsequent commentary for more information. Briefly, there are no longer any database tables required for the Calendar ICal module. If the tables never existed in your database, the update.php script still attempts to remove them, resulting in the error message.

This release contains database updates, so make sure to backup your database and then run the update.php script. It's all in our instructions in maintaining your version of Drupal 5 on your VPS.