drupal module

The Hide Node Links module is a very simply module that allows content authors to determine the visibility of a node's $links on a per node basis, a module that we created earlier in the year and subsequently released back onto Drupal.org. Today we gave this module some love and upgraded it to Drupal 7. This gave us a great chance to learn a lot about Drupal 7's new database API, as well as some of the auxiliary hooks and functions related to Entities and Bundles.

User registration plays an important part in many websites. However, asking users to go through the registration process in order to gain their account can be a barrier for some, and off putting for others. We already have so many different accounts littered across the internet, do we really need anymore?

That is where services like Open ID and Facebook Connect come in. They let you use your existing user account from one site (say, Facebook) to sign into or create an account on another. So, how do you enable that functionality in your Drupal site?

A lot of Drupal modules include their own CSS files, which provide default styles for any HTML rendered by the module. These styles may not suit your theme, and you might find that you must override most of them to get the look you want.

Rather than simply overriding all of these styles, it may make more sense to just completely remove the module's stylesheet and start from scratch in your theme.

This can be accomplished by messing around with the $styles page variable in Drupal's preprocesss_page() function in the template.php file.

The branding for Apple's iPhone is memorable with the various "there's an app for that" commercials. What Apple markets is the fact that its platform is enabled by an enormous list of apps that allow users to do anything they can imagine. It leaves customers with the confidence that the iPhone has the capability to provide everything they need in one place.

The Environment Indicator adds a coloured strip to the side of the site informing you which environment you're currently in (Development, Staging, Production etc). This is incredibly useful if you have multiple environments for each of your sites, and like me, are prone to forgetting which version of the site you are currently looking at.

Drupal is set up fairly well for multilingual sites. However, it does make the assumption that each site version will be in a different language. It is quite feasible however, that there be two versions of a site in the same language. For example, A site which has a UK version, and a version for the Republic of Ireland. Both sites are written in English, but the content varies for each.

Rotor2.1 is out - Just a couple of months since the initial 2.0 release, and with a decent amount of in the field testing, The new Views based approach has gone down a treat, and I've had nothing but positive feedback. The 2.1 release contains a nunmber of important fixes and enhancements, and all Rotor users are urged to upgrade.

With version 2 of the Drupal Rotor module getting closer to a stable release, I decided to launch a dedicated Rotor demonstration site. It's a simple Drupal sandbox which allows people to login and have a play with the new version of the module, in order to help evaluate weather it's right for them or not.

Another Drupal 6 module port in the bag. This time for the IP to Country module, which provides a simple API for retrieving country information such as country code, country name, flag, network name, and autonomous system number by given IP address.

I've been using Ubercart pretty heavily over the past couple of months, and whist I think its a really great bit of software, it still doesn't do all that I need it to out of the box. I wanted the ability to add one off fees to products. Booking fees, registration fees, materials fee etc. Rather than just including these in the products base price and writing about them in the products description, I wanted a more systematic way of managing them. So I wrote: