Recently i noticed hard drive space mysteriously vanishing on a company netbook. The problem was non intermittent and every byte of free space created was soon written to. The likely suspect was a log file but nothing in /var stood out as the offender.

A quick disk usage scan with Baobab revealed that the file was located in a user directory. Manually checking file sizes through thunar revealed the .xsession-errors file to be the culprit. Ballooning to a hefty 1.6GB it effectively made the system unusable.

User contributed module views does not clear on cron runs. This is by design. The cache must be cleared manually through the views UI using the views --> tools menu.

Views queries and pages cached for months or years can wreck havoc on your MYSQL database. Recently a client had enabled views caching and reported intermittent MYSQL crashes.

The culprit was the servers database backup process dying every night it tried to backup a particular Drupal database. This DB was over 5GB all due to a cache_views_data table that was 7.7 GB.

A recent routine Drupal installation revealed a terrible bug that's easy to fix but takes hours to pinpoint. Recently what should have been a 10 minute install turned into a 4 hour job.

The complications arose while installing a fresh instance of Drupal into a multi site configuration. Drupal.org advices that contributed modules may possibly prevent a successful install.

Few would argue that when it comes to uploads an internet application that provides the ability to upload in bulk is superior to one that doesn't. Drupal lacks this feature and must rely on contributed modules to accomplish the task.

The following have been evaluated for inclusion in recent projects.