In the community

As a Drupal site administrator, you may notice in the website logs that there might be a large number of repeated log messages along the lines of "An illegal choice has been detected. Please contact the site administrator." We recently had this problem on a Drupal site that was upgraded from Drupal 7 to Drupal 9 which featured a product search that was built using Views. Due to slight differences in the way in which...

A common requirement for any website that sells products is to have a mechanism in place that ensures orders placed on the website are 'Exportable' - being made available as a file that can be sent across to a different system, to handle the processing of the order. The Drupal Commerce 2.x module (for Drupal 9, 10) has the concept of order 'Workflows', along with defined 'States' and 'Transitions'. A workflow is a set of...

One of the 'new' features in Drupal 10 is that it has removed lots of deprecated code. One of the things that means for our Drupal 10 upgrade project is that some of the modules that this website used are no-longer in Drupal core. Either there's a replacement for each one or they are simply in contrib-land and not supported using the full resources of Drupal core. We'll go one by one looking at the...

One of our big Drupal 7 to Drupal 9 migration projects included bringing across image cropping functionality and data on a longstanding client's website. This site had used the Imagefield Crop module, but that was only for Drupal 7. We set up Image Widget Crop for the new site, which is better in a few ways but is also fundamentally different. The old site referenced the cropped images from content, only bringing in the originally-uploaded images for edit pages, to allow editors to adjust the cropping, which was then used wherever that image appeared on the frontend. But the new Image Widget Crop module allows configuring different crops for different situations. The real challenge was in migrating the data! But we call ourselves Drupal experts, so of course we dug to find solutions. We found the following steps were necessary...

Years ago, when Drupal 8 was released not only did it usher Drupal into the modern age of PHP frameworks and CMSs but it changed how Drupal upgrades were managed and controlled. Gone were the days of painful major upgrades with frequent compatibility breaks; instead we got lovely 6 monthly upgrades that added functionality followed by occasional major releases that removed old code and marked certain features as old ('deprecated' in technical jargon). Several years...

This one is entirely on us, we wrote the custom code, which makes us responsible for maintaining it. The upgrade status module gives us a nice report of each custom project and what changes it thinks are required to bring the code up to date to work with Drupal 10. We really don't have a lot of custom module code, and the code that we do have is very simple, standard Drupal 8/9/10 stuff, so...

We're continuing our series on upgrading this very website to Drupal 10...but our first proper bit of work to upgrade this site is essentially nothing to do with Drupal 10! We built this site in the early days of Drupal 8 and Drupal core didn't really handle 'media' any differently to Drupal 7, but we wanted to try out some new modules that included having a library and drag&drop upload. However, these modules are an...

Let's define the scope and goals of our project to upgrade this very website to Drupal 10. Essentially, that's it: we want to upgrade this website to Drupal 10 so that we can benefit from security releases etc. At the moment we want to do so with the minimum of effort, so I don't want to have to be writing lots and lots of code or changing fundamentally how the site works, but I am...

On 14th December 2022 Drupal 10 was released. We can't say we immediately set about the task of upgrading all our Drupal 9 sites, but we did start thinking and planning to move all our sites in 2023. I thought it might be fun to take a look at how we do an upgrade and specifically the upgrade of this very website. So over the next few weeks we'll be slowly getting this site ready...

Drupal provides an excellent sanitisation system to filter the HTML content that editors might create. Think of it like a series of traffic cops that filter different vehicles into different lanes. Some content is allowed through to its destination, some has to be transformed along the way, and some is simply blocked from displaying. Administrators can use the 'Limit allowed HTML tags and correct faulty HTML' option to configure which HTML elements and attributes they...