Because I often duplicate a production site on a local machine in order to do some debugging/bugfixes, I like everything to be ready the sooner as possible without having to do a lot of clicks.

Here is how I override values in my custom settings.php file instead of loosing time clicking into the administration pages or even doing configuration alteration with Drush.

Here is a common production site settings.php $conf variable alteration :

What do you think this code will output:

If you answered NULL, 0 or '7rray', you're absolutely wrong. The magic with PHP is whatever you use (int) or intval() you get absolutely weird results, because it'll try to parse your string as an integer whatever is in it.

Some months ago, I was developing some Drupal modules for my Company, I noticed the time I loose each time I have to run a Drush command (such as clear cache) in order to do basic Drupal developer stuff.

Today I released the System Theme++ module on drupal.org. This module is a simple administration theme admin page alteration.

I’ve been deploying a new Django application at work with Apache and mod_wsgi (it’s now the recommended way, instead of mod_python) but that still painful and slow to serve static content.

Today, I found the strangiest bug of the month; I was parsing some date parts with JavaScript to properly set default month of a YUI Calendar instance.

Why -1? Because month count starts with 0 in YUI Calendar, January is 0, december is 11; everything is fine until here.

Why the FUCK does my calendar always get to december?

The first official supported version of Yamm has been released1.

This version is identical to the one we use in pre-production environment for some projects. You will have no surprises using it.

Every opinion, feedback or issue is welcome.

I am currently writing a mass synchronization module for Drupal, based on eavy objects abstraction.
I will not describe it here, you can read the project page which describe pretty well how it works.

I wanted to do some notes about development context, and some other stuff.

Drupal node form is not the most exciting user experience that Drupal may propose. If you are an experienced user, there is no need to worry, but in most cases, the sites you'll make with Drupal will be stupid end-user oriented.

With some minor custom theme alteration, you can easily provide the exact same form, but more "Wordpress-like", understand here, with a better organization and a more trivial visual schema.

I dont know how much people get to this problem, but one thing is sure: when you have a paranoid sysadmin, you might encounter some surprises with PHP and globals.

The annoying case is here when you restrict PHP to the maximum you can, you can't access to the $_REQUEST superglobal.