Skip to main content

Assuming there is a new field requiring a change on a content type. How do you ensure the changes apply in the next deployment?

There are a couple of ways to achieve this... depending on whether a custom module exists or not.  I'll focus on using Drush.

Drush is a great tool to manage many of Drupal's features.  For changes that are applied within the backend, best to use Drush export command - drush cex.  Then your config directory at root will be updated with the change.  So when you git add/commit/push, whether via lando or any other plugin or not, the next environment has the change ready to be applied.  Write into your pipeline for drush cim (Drush import to occur).  These actions will ensure the changes are applied in the next deployment.

Related articles

Andrew Fletcher04 Apr 2025
Managing .gitignore changes
When working with Git, the .gitignore file plays a critical role in controlling which files and folders are tracked by version control. Yet, many developers are unsure when changes to .gitignore take effect and how to manage files that are already being tracked. This uncertainty can lead to...
Andrew Fletcher26 Mar 2025
How to fix the ‘Undefined function t’ error in Drupal 10 or 11 code
Upgrading to Drupal 10.4+ you might have noticed a warning in their code editor stating “Undefined function ‘t’”. While Drupal’s `t()` function remains valid in procedural code, some language analysis tools — such as Intelephense — do not automatically recognise Drupal’s global functions. This...
Andrew Fletcher17 Mar 2025
Upgrading to PHP 8.4 challenges with Drupal contrib modules
The upgrade from PHP 8.3.14 to PHP 8.4.4 presents challenges for Drupal 10.4 websites, particularly when dealing with contributed modules. While Drupal core operates seamlessly, various contrib modules have not yet been updated to accommodate changes introduced in PHP 8.4.x. This has resulted in...