Wrestling with an error message on a Drupal Commerce site today. I kept getting errors relating to a missing template file with no path and no file name .tpl.php. Fortunatley with a little debugging giving me a pointer to the correct issue queue on Drupal the solution was readily available. So here's a few easy steps to follow in case you have the same issue.

Getting your page title and metatags correct is great for SEO and enables your readers to locate your content by getting it indexed well.
In this post we'll see how to get your modules and theme to play nicley together to ensure that your page structure is optimal for web standards and indexing. In most cases this can be sorted with a simple fix.

If you use the Ubercart module suite for Drupal to create e-commerce sites (we do and love it!) then one of the things you may wish to do is to change the default 'cart' to 'basket' - for a non-US audience. There is no setting in the Ubercart modules to enable this - but it is really easy and here's how to do it.
Get the excellant string overrides module and install it. Then set it up to swap the following fields:

Original - Replacement

Drupal is great and the taxonomy system is great - but large taxonomies (over 1,000 terms are a headache for any system) and Drupal is no different. I have a new taxonomy for a project with > 5k terms in a three deep hierarchy and using it presents some usability, performance and other issues.
So I though I would take a break and write a bit about evaluating some Drupal contributed modules for working with large taxonomies:

A general housekeeping task for CMS systems such as Wordpress and Drupal and other websites and good practice to keep your site SEO high is to make sure you are gracefully handling missing pages (404 errors).
One of the routine tasks to carryout is checking for crawl errors in Google Webmaster tools. If you see any missing pages in the list it is worth making sure you have some measures in place to handle these and ideally issue a 301 redirect so that Google and other search engines update their indexes.

It ducked!
Monday morning the sun is shining and your email box is full of emails saying cron is failing on one of your sites.
In this post I will look at what is going on, how you can troubleshoot it and fix it and how life may be made easier in the future by a) adding a bit of logging to cron and b) features in Drupal 7.

Some modules use the same hook and therefore are 'called' in succession. Sometimes you would like (need) a particular module to fire after or before other modules. An example is the XML site map module that would best fire after the pathauto module to ensure that the site map contains the final version of the urls used for pages in your site. There are a number of ways to manage this -

When you first install Drupal it creates the master user (1) - this should ideally not be used to create content and it is good practice to create a new user for administrative purposes (not called admin but with an equivalent set of permissions) and an administrators group so that the super user doesn't get used - it may even be worth blocking the super user once you have done that. But be aware that some modules need to impersonate that user. If you want to restrict login for that user you can create an Access Rule to deny Admin for user name - this will effectively disallow logging in as Admin.

Quick note: On a site I worked on recently I made a change to the Pathauto settings and needed to create a load of Redirects for previous URLs. Fortunately there is a quick way to do this using wildcards in the htaccess.

One of the most frequently asked questions for a new Drupal installation is - How do I get the search box to show? The answer is go to Modules and locate the search module in the core modules and enable it - it is disabled by default. Another gotcha here is checking your permissions and ensuring that users have access to search and other facilities.

See your first user permissions and roles