Like many small consulting shops, we often work with developers scattered around the world. Recently a Drupal developer delivered a custom theme to us, with a SQL snapshot of the database he had been using to work on it. We installed the new database and eagerly tried out the new theme, only to be met with a slew of error messages of this format:

# warning: Invalid argument supplied for foreach() in 
/home/jon/Workspaces/php/secretprojectx/includes/theme.inc on line 463.
# warning: Invalid argument supplied for foreach() in 

Last month saw two new Ideograph projects come to completion.

• GreatWorkPerks.com, a website for a Los Angeles based firm that lets employees take better advantage of perks available them through their workplace.
• myEARTH360.com, an eCommerce site for the well-known retailer of eco-friendly products.

When building a new Drupal site with a custom theme and a custom module for a project, it seems reasonable to give both the same name — the name of the client, say. But this turns out to be a terrible idea, for a non-obvious but educational reason. Read on for the details.

A new client is leaving GoDaddy's low-quality Quick Shopping Cart product in favor of Drupal and Ubercart. We've stepped in to help them migrate their product data and set up the new site.

Code is much easier to read when its different syntactical elements are colored differently. Modern IDEs do this automatically, but when pasting a code fragment into a webpage it is normally just displayed in a monospace font. We recently installed the GeSHiFilter module, which colors code syntax in our pages automatically. Here's how we did it.