- Issue created by @wim leers
🐛 Disabled SDC components are re-enabled after cache rebuild Active fixed auto-reenabling of disabled SDCs. But there's one (fairly rare) edge case it doesn't solve:
foo
installed that provides a hello
SDCfoo
, then the sdc.hello
Component
config entity will be disabled by \Drupal\experience_builder\Entity\Component::onDependencyRemoval()
foo
because I realize my mistake, then sdc.hello
will start working again … but it will not appear in the list of available components in the UI anymore, because it remains disabledUpdate \Drupal\experience_builder\Entity\Component::onDependencyRemoval()
to store the reason (\Drupal\experience_builder\ComponentIncompatibilityReasonRepository
) for a component getting disabled — here that is: "dependency was removed" or something like that.
Now use the presence of that very reason as justification for conditionally calling ::enable()
again.
Because the bug that #3526967 fixed was that it was being called unconditionally.
Active
0.0
Config management
Enhances developer experience.
Makes Drupal easier to use. Preferred over UX, D7UX, etc.