Gergely Lekli's blog

With mobile devices being so popular, web users increasingly use mobile browsers instead of desktop browsers to surf the web. Developers and designers need to keep this in mind when building web sites to avoid potential revenue loss due to web pages being unattractive or unusable on mobile devices.

Although the CCK3 module had never seen a full release, it was still worth upgrading Drupal 6 sites from CCK2 to CCK3, because the latter added a very compelling tool to CCK's arsenal: Multigroups. This feature allowed users to group several fields together, and enter multiple values into that set of fields as a whole by repeating the field group whenever a new value is added. For instance, let's suppose your node has an event multigroup containing date and location data.

Mobile devices are gaining incredible popularity when it comes to accessing web content. Web site owners and web developers are facing the challenge of having to serve all the needs of mobile users as well as web users. I have recently been given a chance to work on a Drupal site that serves web users and mobile users from one singe Drupal installation.

Drupal has a setting that allows you to put the site off-line, and show a maintenance message to the visitors. However, in order to determine that the site is in off-line mode and load the maintenance page, Drupal still needs to boot up to some extent, which involves loading several PHP files and connecting to the database. This may lead to the visitors seeing error messages, if the site is being tampered with while they try to access the site.

At Urban Insight, the Kaltura video platform is one of our favorite video hosting services because it has excellent support for mobile devices. Uploaded videos can be converted to mobile format, and when Kaltura code is embedded in a site, videos play nicely on virtually any mobile device. Unfortunately, the Kaltura Drupal module does not currently provide effortless support for the Kaltura HTML5 player feature.

In connection with the recent launch of a high-profile Drupal-based website, one of my responsibilities was to evaluate how well the then un-launched system would perform under the expected load. As a web developer, I don't often have the opportunity to do load testing, so I had to do some research on the topic beforehand. This post is a summary of the steps I took and my findings.

One of the most versatile Drupal modules, Views, comes with an impressive user interface that allows you to capitalize on all its functionality – or does it? Although this interface is the primary means of using Views, the module has plenty to offer on the code level too.