Drupal

I was really impressed, back in 2013, by Alexandru Badiu's (@voidberg) presentation on Behat delivered at Drupalcamp Târgu Mureș. This year, Konstantin Kudryashov (@everzet), the guy behind Behat, Mink & phpspec2, had its own presentation at Drupalcon Amsterdam. And it was again — Wow, wow! Since then I never found the right time to play and experiment with Behat until I got stuck in providing a tested UI for a site having very complex frontend/jQuery requirements. And for me that was the right time for Behat :)

This writeup is heavily based on Karen Stevenson (KarenS) blog post Sending a Drupal Site Into Retirement. The reason for writing this post was to keep a Webikon.com reference, facing the requirement to archive several sites and make them static. True, there are also some small differences.

Keeping file system with secure permissions has been always a critical task when it comes to administer a webserver. Not every time files uploaded via the webserver are saved with the correct permissions. Running a cron job to fix them could be a solution but how to deal with the case when an attacker can very quick exploit files wrong set permissions?

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!