Skip to main content

Lee Rowlands

Lee Rowlands
Senior Drupal Developer

Location

Bundaberg

Lee has 17 years professional development experience with PHP, is a member of the Drupal.org security team and maintains the forum, comment, contact and block content modules in Drupal core along with at least 30 contrib projects. He is also the framework manager for core.

My blog posts

Using Behat and DrupalDriver? Beware pathauto.

by Lee Rowlands /

Here at PreviousNext we love behat. We use it as part of our CI builds to make sure that we're not introducing regressions and it's a great fit for our Agile methodologies. But we recently had some issues with weird behaviour in our tests, such as page manager pages not working. Read on to find what was the cause and how we tackled them.

Read the full post

Setting priorities for Drupal 8 in the lead up to code freeze

by Lee Rowlands /

The Drupal 8 code freeze on July 1st is a bit over a month away.

In light of this fast approaching deadline I felt it was time to reassess my list of 'must haves' to focus my priorities for the next four weeks onto the issues that matter the most to me.

Here are my the ten issues at the top of my list. Want to share yours? Leave us a comment

Read the full post

Understanding Drupal 8's Modal API and Dialog Controller

by Lee Rowlands /

It is common knowledge that Drupal 8 contains Views module, thanks to the work from the Views in Drupal Core (VDC) initiative.

Our contribution to the VDC initiative was working on abstracting Views UI's modal pattern into a generic modal API in core.

Recently one of the coolest pieces of this API was committed to core.

You can now load any content in a modal simply by adding a class and an attribute to any link.

Sound cool? Read on to learn more.

Read the full post

A recipe for a sane git process in Drupal's patch based workflow

by Lee Rowlands /

Drupal uses a patch based workflow. Changes to core and contrib projects are suggested in the form of patches attached to each project's issue queue. This is nothing new.

But this is not the norm for projects that use git for version control. Normally they use a traditional git branch/fork process - issues are worked on in branches or forks, when ready a pull request is sent, when approved the code is merged.

The git workflow has a number of advantages over the patch workflow, the most notable being there is no need to re-roll patches - you just merge HEAD instead.

So given Drupal uses the patch workflow, this article shares what I've found to be a successful recipe for maximizing the features of git in the patch workflow constraints.

This recipe has several advantages, including ease of creating interdiffs.

Read the full post

Tour Module Part 2: Creating a Tour for your module

by Lee Rowlands /

Drupal 8 comes with a new guided help API in the form of the Tour module. PreviousNext put a lot of effort into getting this module into Drupal 8 core prior to feature freeze and are excited by the possibilities it presents to ease the learning curve for new Drupal site-builders.

In part 1 of this post - we told the tale of how this module came to fruition. In this post, part 2, we provide examples of how you can add tour module support to your modules and talk about some of the advanced features of the API.

Read the full post

Tour Module Part 1: The Journey of Adding a Drupal Feature

by Lee Rowlands /

Drupal 8 comes with a new guided help API in the form of the Tour module.

Here at PreviousNext we were instrumental in getting this module in prior to feature freeze and are excited by the possibilities it presents to ease the learning curve for new Drupal site-builders.

In this post we discuss how the module came about, how we went about building support for the idea and the way the API works.

In part two we will go on to show some examples of how you can add tour module support to your modules and talk about some of the advanced features of the API.

Read the full post

The Drupal 8 Patch a Day Challenge

by Lee Rowlands /

We've entered the clean-up phase of the Drupal 8 release cycle. Drupal 8 is shaping up to be the best Drupal release to date - with a raft of new features and a less Drupal-centric developer experience.

So the question on everyone's lips is, when will Drupal 8 be released? The answer is the same as it has always been, 'When it is ready'!

We can't wait to start working with Drupal 8 on a daily basis. The new features will make our day-to-day jobs so much easier and our development workflow so much cleaner.

So to this effect, I'm aiming to work on one patch per day from now until the Drupal 8 release.

Will you join me in the Drupal 8 Patch a Day Challenge? Read on for more details.

Read the full post

Understanding Drupal 8's config entities

by Lee Rowlands /

Drupal 8 comes with a new type of entity, a config entity.

Those working with Drupal 7 will be familiar with entities for their content.

Drupal 8 introduces the concept of a config entity, which is very similar to a CTools exportable in Drupal 7, but with much of the entity system goodness.

Read the full post

Collecting and writing configuration settings to setting.php from an install profile

by Lee Rowlands /

We've recently been working with one of Australia's television networks to build an installation profile that will form the basis of migrating many of their existing sites to Drupal. One of the interesting challenges in the project has been handling collecting additional configuration and settings during the installation profile, but before the database is installed.

Read the full post

Pagination