Contrib.social

does config ignore need a config file to ignore?

Open on Drupal.org →
Created on 29 August 2017, almost 7 years ago
Updated 4 January 2024, 6 months ago

Let's take this scenario:

I have a live site with config that is changed by the site admin.
I have a new set of configuration files.

In one case there is active configuration in the database for a form, but there is no configuration file for it because it is config-ignored.

On import, the config fails to validate because there is no configuration file for this one piece of active configuration.

My panicked solution was to drush cdel the offending config and run the import, and then go back and enter the settings once again.

Is there a better way? Does config-ignore require the configuration file to be present in order to be able to ignore it?

💬 Support request
Status

Closed: outdated

Version

2.0

Component

Miscellaneous

Created by

🇮🇪Ireland anthonylindsay

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.

  • 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