The recent update to Google Chrome dev (Version 23.0.1262.0 dev-m) has brought rulers to the window when using the Inspect Element feature which is becoming increasingly better with each release. Firebug usage from me has significantly dropped.

It took a while to figure out with all information I could easily find relating to the Rules module using the UI to define rules.

But you can define some default rules within your module by using the function MODULE_NAME_default_rules_configuration() which sits within a file called MODULE_NAME.rules_defaults.inc in your module folder.

What are we looking to do?

When you have an online store, by default a product has a set price which is what everyone pays. You may have discounts through voucher codes but occasionally you want to offer a different price to shoppers i.e. wholesalers.

So what we will be doing is creating a new role called 'Wholesaler', adding a new price field to our product, then we will set up a rule which will calculate the right price for the wholesaler.

The tutorial will be focused around a basic Drupal 7 install with the Commerce module (and the other relevant modules installed).

Geocoding UK addresses has always seemed to be a pain especially outside of Drupal. With Drupal 7 a few of the mapping/location modules that I have been used to using in Drupal 6 are either not available as a stable release or don't quite do what I wanted. A key example is Location which I have used on a Drupal 6 with which geocoding has never worked (I still don't know if it is something that should work out the box, it certainly seems to imply to me.)

A rash of new Drupal 7 modules has made the process a lot easier though.

Anchor CMS is getting more attention as of late with one of its key features being able to add custom javascript and CSS per blog post. This allows a lot of custom design to take place which differs per page. An example of this can be found on the creators blog.

Drupal is lacking this feature, but as is the way with Drupal, "there's a module for that". Code per Node does this and more allowing you to add custom CSS and javascript to both blocks and content types as a whole rather than individual nodes.

Site is very simple just using a basic view for the blog listing (which I could of just used the standard river of news, but it's nice to know that I can control it whenever I want).

The upgrade process was very simple, there were a couple of issues with modules not working properly mainly due to PHP 5.3 errors but they were easy to overcome or I just got rid of the module as it wasn't really needed.

I have been playing about with creating my own base theme which I can use to easily roll out new sites quickly and easily for those who don't want to pay for a bespoke design.

The main problem with this is ending up with one theme for all, to get around this with out having to do any development work is use Drupal's core colour module which allows the user to select the colours of certain areas.

This will just show you the basic code that is required for use with a theme using the PHPTempalte engine with some comments on what the code is doing at parts.

Sorry but I will be using the English spelling, too used to typing with the 'u'.