Why Drupal?

Drupal is the leading open source content management system for developing sophisticated, flexible and robust websites, social media networks and applications.

While working on a custom bootstrap subtheme in Drupal, I needed to include specific classes in the body tag. There are two different cases that I needed to take into consideration, one for nodes and one for custom paths generated by e.g. from Views or Taxonomy. In the first case, I needed the node id to be included as a class, and on the second I needed a class name that was based on the path. To achieve this, I needed to edit two different files under my subtheme category. You will need to replace themename with the actual name of your theme.

A weird issues came up after upgrading from Views version 7.x-3.7 to 7.x-3.8. The pager was missing from all views. After making sure that there are enough results to bring up a pager, and that the pager ID was unique for each view that shows up in the same page, we noticed the one thing that all views had in common: They all used Global: PHP fields. It seems that this is a known issue and that there is a patch that people confirm it works.

A request that often comes up is to change the order of the Addressfield fields.

Heartbeat messages were showing up nicely on a project we have been working on lately, bringing up all the member activities including changing the user account details, adding or editing nodes and commenting on nodes. Everything was working fine right out of the box - except one minor inconvenience that we noticed: all comments were showing up twice in the heartbeat stream. As many love to say, this is not a bug, it is a feature.

Drupal 7 has the ability to run cron automatically, but if there are tasks that really depend on cron, it only makes sense to ensure that cron is running in pre-defined time spans.

To make sure of that, we can configure the drupal cron to run from a server side command. So from the console, In crontab, the following line will trigger Drupal's cron

Here is a useful snippet that you can use to change an already existing drupal textfield into a text area.

If you do not want to use i18n_string and i18n_field in order to translate the Order total, Shipping & Billing Information texts, that show up in the cart and on the checkout pages when using Drupal Commerce, the following hacky approach should do the trick.

First, the following funcion can be used in your template.php file:

Here is a nice little PHP snippet that will remove non-ASCII characters from a String. Code was taken from here.

Here's a snippet that will rename the edit tab to a custom string, on node edit, depending on the content type. It is easy to add different or additional validation criteria, depending on when you would like the Edit tab to show up with its brand new name. This code should be placed in a custom module.