Imagine this scenario: We have a view of certain content type nodes. This content type has field of type taxonomy term reference and we want to filter the view by taxonomy term ID. It means, we only want to display content assigned to particular taxonomy term. Easy, right? Obviously, you'd create this view on your local or development environment. Then you push the configuration on production and what??? The filter does not work! Why? Because the ID of the taxonomy term may be defferent on production website.

Recently I was working on a project which required webform and some webform workflow. To my satisfaction I used the Webform Workflows Element module which provide a simple workflow element using the core Workflow module. This module provides simple element to expose a workflow into the webform submission. Basically, you can set the state of the submission and, if you want, provide log messages. One for admins, one for submitter. Exactly what I needed.

I'm doing a site upgrade for a client from Drupal 6 to Drupal 9. This time I decided to dive deeper into the Drupal Migrate API and use it to migrate content. Everything was going smoothly until I ran into image migration. I migrated the files themselves without problems, as well as the content, the only thing I couldn't do was link the file entities to the content entities. On the old (Drupal 6) website they were in the field_news_images, on the new one the field is called field_images.