An part of operating a Drupal site is to keep the site's code up to date. Updates to Drupal core and contributed modules provide enhancements to functionality as well as critical fixes to security vulnerabilities. Here's a rundown of the process I just used to update this site.


Everybody has heard of cron, but what exactly happens during a cron run? Let's take a look at Drupal core and some common contrib modules to see the type of tasks are handled during cron.


I recently completed the process to get vetted access in order to create Drupal projects. It's a fairly simple process where you create a sandbox project, create an issue in the Drupal.org Project reviews queue, and once the project has been reviewed and accepted you're granted access to promote the sandbox to a fully-featured Drupal project. This process is in place to educate maintainers of best practices and Drupal standards as well as encourage a high level of quality for projects featured on Drupal.org.


One of the most useful tools for developing and managing Drupal sites is the drush command-line utility and one of the most common rigs for Drupal development is the pre-configured MAMP stack. Unfortunately this doesn't work right out of the box so before you go futzing-around trying to get it to work, let me show you the easy way.


When you need Drupal to do more stuff, the general course of action is to first peruse Drupal.org to find a module that suits your needs. How do you know which ones are safe to install and which ones will suit your needs?


If you've got development workflow where you're frequently switching among environments, it's easy to get confused about which site you're on. Even the best of us are known to have a little oopsie every now and then so before you go changing site configurations or restoring database backups, you better be sure you're not mucking up the live site. Here's a nifty little module to help you keep things straight.


You've poured your heart and soul into a site, you went down the final checklist to make sure you didn't miss anything, and the site was perfect when you launched it. Everything's been running smoothly for months but now... Well, now it's acting crazy. What do you do?


One of the easiest things you can do to give your website a professional appearance is to use the Path module (core) to enable pretty URLs/aliases and the Pathauto module to automatically generate aliases. Sensible alias configurations give your site a nice, polished look as well as make your content search engine friendly by including node (user and taxonomy, too) data in your URLs.