I'm using more and more views on DrupalMU and I needed a way for the pages and blocks to be blog-centric. When you're on a specific blog you only want to see the recent comments on that specific blog, or only see the archive of blog entries by that owner. You also want the blocks to appear on any page of which the blogger is the owner: the user's profile, his blog entry listing, a specific blog entry, the comment page of that entry, ...

I regularly come across a client's Drupal database and see that it's lingered with left-over tables and settings. These tables are often from modules that were installed during previous Drupal versions or that were ditched altogether. Here's a good tip: uninstall a module before deleting it. Most modules come with an uninstall function that cleans up any used tables and variables, keeping your database nice and tidy. Do note that you still need the module on your server to be able to uninstall it.

As mentioned in my previous post I'm working on end-user documentation on how to install an installation profile. I've now come around to publishing the first draft.

This is an update of the old and outdated article "Drupal member list" which was written for Drupal 4.7 and Drupal 5 when it was just released. This article applies to Drupal 5 and 6.

GHOP student Philip W has done an amazing job creating much-needed documentation for the new asset module. Especially the guide on integrating assets with TinyMCE will help out a lot of people. Thanks for this Philip, your work is highly appreciated!

In this process two bugs were identified and fixed (in the newest dev version) and work is being done on two critical issues. Alpha 3 will be released soon after which I hope to release the first beta. In the meantime Roger Lopez is working on a rewrite in HEAD so these are really exciting times!

I'm doing a presentation on file- and media-processing with a focus on the asset module at FOSDEM and Roger Lopez proposed a session at DrupalCon Boston. If I make it to DrupalCon I will co-present the session but this will only be the case if I aquire some funds to get me there.

Earlier this year I wrote a small guide on what to do when you're experiencing character encoding issues after upgrading MySQL to version 4.1 or higher. Now after a large combined effort with JirkaRybka a documentation page is set up in the Troubleshooting FAQ: MySQL 4.0 -> 4.1 migration.

This guide includes background information, a description of several issues when upgrading MySQL and a solution for each problem. You no longer need to manually change update.php (cfr. my earlier guide) since a stand-alone script was written that works for Drupal 4.7, Drupal 5 and Drupal 6! This is very important since Drupal 6 will require you to have MySQL 4.1 or up, if you're using MySQL of course, and this will make upgrading so much easier, saving people a lot of precious time debugging. This documentation and the script are all a combined effort of JirkaRybka, Heine, Acert93 and myself.

You can check the original request by Acert93 to provide more information on this issue and see how this documentation came to be.

This night the host of a client upgraded from MySQL 3 to MySQL 4.1. It is a known issue that his might bring problems regarding character enconding, resulting in special characters (like acute accent or umlaut) or getting defaced. Some of these issues can be resolved quite easily, for instance the user error "Illegal mix of collations". We'll first look into what happens behind the scenes when upgrading from MySQL 3 or MysQL 4.0 to MySQL 4.1.