Drupal

Understanding advance page template preprocessing

The main role of the page preprocessor is to set up custom variables to be rendered through the template (.tpl.php) files. Mostly the page preprocessing is used to handle theme template suggestions. This means that based on some custom logic we can suggest any page--*.tpl.php file instead of generic page.tpl.php but this is not the limit, most advance developers use these preprocessors to do heavy calculation of their logic and then pass the results to the page.tpl.php in form of some custom variable, this avenue has endless possiblities.

How to get In-Field Labels in Drupal 7

Compact forms are always good to have and in-field labels is one of the feature that makes the form more compact and sleak. Conventionally the labels are set as "above" or "in-line" with the fields where as in-field labels are set with in the Label's respective fields. Technically form item or element fields are overlaid with their repective labels.

Migration Solution to Taxonomy Vocabulary Relate Module in Drupal 7

Taxonomy Vocabulary Relate was very helpful module in Drupal 6.x which allows us to select related terms in taxonomy from other vocaulary. Default taxonomy module in Drupal 6.x only allow us to select related terms from the same vocabulary. This post is going to help lots of developers who are planning to migrate their Drupal 6 website to Drupal 7 or who have migrated their projects and are awaiting solution to this issue.

Enterprise Portal in Saudi Arabia's Leading IT Organization

Last week we successfully implemented Drupal as an Enterprise Portal for one of the largest IT Organization (Saudi Business Machine - SBM) in Saudi Arabia. Portal is very much optimised to support  50,000+ user base, portal has been developed over the course of six months with handful of resources.

Intranet of 90K+ developed on Drupal for a Fortune 20 company

I am glad to be part of a team who deployed Drupal as an Intranet platform for a Fortune 20 telecom company.  This is the first time that Drupal was used on an open surce LAMP stack to create a corporate Intranet for over 90,000 employees. The project was a complete rewrite of the existing intranet that had been in operation for over half a decade. It was accomplished in less than 12 months from conception to full deployment, ramping up from just a one member team to a 17 person group with only 5 full time developers