Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Problem/Motivation
There's lots of configuration that references plugins.
Sometimes modules own both the configuration and the plugin (i.e. Field API).
Sometimes not (Views and Field plugins).
If a module providing a field plugin renames or removes it, what happens to all the configuration that references it?
Proposed resolution
Probably needs to be based on #2080823: Create API to discover config entities' soft dependencies and use this to present a confirm form on module uninstall, except you'd also need to be able to update the configuration based on the change.
Remaining tasks
Lots.
User interface changes
Maybe.
API changes
Some.
Comments
Comment #1
catchComment #2
catchComment #3
xjmComment #4
moshe weitzman commentedThis strikes me as a normal bug, but lets split the difference.
Comment #5
alexpottWe need to have a actually problem to solve otherwise we're likely to come up with an non ideal solution.
Comment #6
xjmTo clarify @alexpott's comment, we will keep this open to watch for issues as we begin to provide upgrades during the beta phase, and revisit before release to see what steps we might need to take.
Comment #7
xjmComment #8
alexpott#2260457: Allow config entities to remove dependent configuration keys when dependencies are deleted due to module uninstall will help with the situation where a module that provides a plugin goes away.
Comment #9
xjmComment #10
xjmNotes on this issue from DrupalCon Austin:
https://docs.google.com/a/acquia.com/document/d/18R3-k0saR_RCZBYnggM0B8b...
Action items:
https://docs.google.com/a/acquia.com/document/d/18R3-k0saR_RCZBYnggM0B8b...
Comment #11
xjmComment #12
xjmPer discussion with @alexpott today, this also might be something we end up shipping in 8.1.0.
Comment #13
xjmComment #14
tim.plunkettComment #15
xjmRelated issue posptoned to 8.1.x: #1977498: Add version tracking for configuration schema and data
We agreed to keep this issue marked for revisit before RC, since we are far more likely to change e.g. plugins than schemata.
Comment #16
catchComment #17
mgiffordOk, no need to postpone any more.
Comment #18
xjmDiscussed with @catch, @alexpott, @effulgentsia, and @webchick. This can now be closed as a duplicate of #2538108: Add hook_post_update_NAME() for data value updates to reliably run after data format updates.