Drupal 8

Sooner, the European Commission Drupal project I'm working on, will transition to a new theme. During the transition, some pages will be still displayed using the the old theme. I've looked around for a Drupal module that knows to render a certain page using a specific theme and found Switch Page Theme. The big impediment with this module is that it mainly checks the page path. And this is more or less hardcoded.

Form Protect is my first Drupal 8 module, even it's a tiny one. First I needed the module for a Drupal 7 client project. But after having the D7 module running, I felt that it's good opportunity to write my first Drupal 8 port.

Recently I gave a short presentation at Szeged DrupalDevDays 2014 about the image system changes in Drupal 8. Here are my presentation slides:

Alkuvoima+East Group, a Finnish strategic digital marketing agency, invited us to join one of their interesting events in Helsinki. We were asked to present some hot topics like: ‟Drupal 8 — What’s Cooking?”, ‟Migrate to Drupal 8” and ‟Drupal 8 as a mobile backend” along with another cutting-edge presentation: ‟Drupal and Apache Stanbol”. The big interest aroused by the ‟Migrate to Drupal 8” topic inspired me to elaborate on this subject.

At Drupalcon Prague 2013 Dries announced the switch to a migration-based upgrade and the move of Migrate module in Drupal core. In this write-up I will introduce you to migration basics: concepts, flow, components and then I will illustrate a complete migration process, as it works, now, in Drupal 8 by explaining how a real migration has been implemented in a real module. Here we go!

Note: The Twig conversion acts here more as a pretext to showcase the power and flexibility of using Apache JMeter™ as a benchmarking tool for Drupal.

Staring with release 8, Twig was adopted as theme engine for Drupal. The conversion of PHPTemplate theme_*() functions and *.tpl.php template require also benchmarking.