Drupal 11.3.6 Regression Linked to Potential Data Loss During Config Imports

Staff Reporter

DDEV v1.24.7 introduces enhanced security with the dedicated ddev-hostname binary

Recent updates to Drupal core have exposed a regression in versions 11.3.6 and 11.3.7 that can lead to data loss during configuration imports under specific conditions.

The issue occurs when multiple modules are installed during a single configuration synchronisation. In such cases, the configuration state is not correctly persisted, which can result in fields or related data being removed without clear indication. The regression is addressed in Drupal 11.3.8, which includes a fix for the underlying issue.

Matthew Radcliffe explains in a community post that the problem can surface in deployment workflows where module installations differ across environments, making it difficult to detect through standard quality assurance. As a result, sites may encounter configuration discrepancies only after deployment.

Sites that performed configuration imports on affected versions are advised to re-import configuration, compare active and staged states, and verify that no data has been lost. If discrepancies are found, restoring from backups may be necessary before updating to Drupal 11.3.8 and running standard update procedures.

Reference: Summary of Drupal 11.3.6/11.3.7 potential data loss and update steps for 11.3.8 by Matthew Radcliffe (23 April 2026)

Drupal 11

Security

Configuration Management

Drupal

Drupal Core

Drush

Disclosure: This content is produced with the assistance of AI.

Disclaimer: The opinions expressed in this story do not necessarily represent that of TheDropTimes. We regularly share third-party blog posts that feature Drupal in good faith. TDT recommends Reader's discretion while consuming such content, as the veracity/authenticity of the story depends on the blogger and their motives.

Note: The vision of this web portal is to help promote news and stories around the Drupal community and promote and celebrate the people and organizations in the community. We strive to create and distribute our content based on these content policy. If you see any omission/variation on this please reach out to us at #thedroptimes channel on Drupal Slack and we will try to address the issue as best we can.