Contrib.social

Loading config admin UI while config is importing causes ignored config to be not-ignored

Open on Drupal.org →
Created on 8 November 2023, 8 months ago
Updated 4 January 2024, 6 months ago

Problem/Motivation

While doing a config import, if the config admin UI is loaded it interferes with the import process and anything which is being ignored is no longer ignored and can be deleted.

Steps to reproduce

Configure Config Ignore to ignore a few items.
Have a configuration that ignores these items.
Make configuration changes that needs to be imported.
Use "drush config:import" to start the configuration import.
While that is running, load admin/config/development/configuration.

What happens:
* The ignored configuration items are no longer ignored, and will be deleted if they are present in the site.

What should happen:
* The ignored configuration items continue to be ignored.

Proposed resolution

Fix the bug (-:

Remaining tasks

Fix the bug (-:

User interface changes

Loading the config admin UI while the configuration is imported using Drush does not

API changes

TBD

Data model changes

n/a

🐛 Bug report
Status

Closed: outdated

Version

2.0

Component

Miscellaneous

Created by

🇺🇸United States DamienMcKenna NH, USA

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

Comments & Activities

  • Issue created by @DamienMcKenna
  • Comment 8 months ago →
    🇺🇸United States DamienMcKenna NH, USA

    Note: this happened to us with Config Ignore 8.x-2.4 and the (then) latest core release in June, we have not tested the problem since then so the bug may have already been fixed.

  • Status changed to Closed: outdated 6 months ago
  • Comment 6 months ago →
    🇨🇭Switzerland bircher 🇨🇿

    This issue is being closed because Config Ignore 2.x is deprecated.

    The new 3,x version has been re-written from the ground up and works in a totally different way, yet it provides the same backwards compatible functionality. All the 2.x tests pass in 3.x and the 3.x codebase is easier to maintain.
    Users of 2.x are strongly encouraged to upgrade to 3.x, as there is a very simple update path.

    So likely this issue is no longer relevant. If you think that this issue still applies please open it again and target the new branch. All issues on the 2.x branch were closed in bulk.

contrib.social Blog FAQ Discussions
Production build 0.69.0 2024