On a Drupal site, when setting up pathauto for nodes, sometimes it is useful to have the full nested path of parent terms of the channel (or primary vocabulary) for the article in the url alias to give the impression of a directory structure to the taxonomy vocabulary. This will allow users to see urls to nodes like domain/term1/term2/term3/node-title-or-whatever where term3 is the channel under which the article is published.

Drupal uses a reasonably powerful mechanism to create, prepare and send emails generated within the system. We maintain two modules related to emails in Drupal - Mail Merge and MailQ (Mail Queue) - and get the opportunity to work with the mail subsystem in Drupal. Here is a brief write-up on how the mail system works in Drupal.

Upgrading a Drupal site refers to moving it’s database and files from one major version of Drupal to a later one, to take advantage of the newer features and bug fixes that might not be available for the older version. Upgrading a Drupal site is a pretty effective way to make sure that your Drupal site is currently up to date with all the latest security updates and bug fixes. Old versions of Drupal will naturally be unsupported with the arrival of the new releases. The Drupal community has currently stopped supporting the older versions of Drupal like version 4 and 5 and has moved to Drupal 7. However Drupal 6 is more widely supported. Have a look at the steps required to upgrade your Drupal site from an older version to      Drupal 6.     

Drupal allows very fine grained control over how content is presented to the end user. The presentation layer is abstracted beautifully and cleanly designed hooks allows for moving data from the logic layer to the presentation layer. The template file that handles the basic page layout of every drupal site is page.tpl.php and the different regions available for a given theme are all available as HTML elements in page.tpl.php. Another important template file is node.tpl.php which decides how nodes are presented to the end user. Normally the content of nodes go into regions inside page.tpl.php and so does blocks and panels. But what if you want to have regions inside the display area of nodes? What if you want to use blocks to display content inside nodes? The answer is simple - template preprocess is the key.