Config import fails silently.

Created on 9 August 2022, over 2 years ago
Updated 20 August 2024, 4 months ago

Config import seems to fail silently in quite a few circumstances, especially when the order, but not the content of the config is different. This is via Drush and the admin UI, with the site in maintenance mode and the cache cleared.

There is a thread with quite a few examples of this here.
https://www.drupal.org/project/drupal/issues/3102549 πŸ› Configuration changes does not get imported Fixed
That thread locked and a maintainer would need to reopen, so I'm making this open issue for people to contribute their examples to, but this issue can be closed if the other one is reopened.

πŸ› Bug report
Status

Active

Version

11.0 πŸ”₯

Component
ConfigurationΒ  β†’

Last updated 3 days ago

Created by

πŸ‡³πŸ‡ΏNew Zealand thomasmurphy

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡¨πŸ‡¦Canada _randy

    This is happening in Drupal 10.1.1 as well.
    After syncing an entire site's config to the target site, I have 106 config files that import just fine, but remain in the Config Sync UI. Only differences are the ordering of the config parameters.

    Manual import via Devel config editor does not resolve the issue and nor does a manual import via the Single Config import option.

  • πŸ‡ΊπŸ‡ΈUnited States SteelStrung

    Also having this issue with Drupal 10.3, PHP 8.2
    I have a development/testing environment and upgraded one to 10.3. After I pushed code to the testing environment and exported/imported configurations, there are several that will show up with 'drush cim' even after it imports. Reviewing the configuration differences from /admin/config/development/configuration/ shows that the differences are mostly just order changes of the parameters.

    #5 has a point about the order changes, but I think Configuration Manager should be fixed to either ignore the changes to order when identifying differences, or it should update the config item order as well so it matches the config being imported (thus no differences).

    It is confusing to see items still needing to be imported in the CLI when there are materially no changes, and the only suggestion is to view the diffs to see if there is really a material change that needs to be imported (seems redundant)

Production build 0.71.5 2024