Display disabled Block components in /admin/structure/component/status

wim leers → credited el7cosmos → .

AFAICT this bug reported by @el7cosmos in #3475584 is in scope of this issue to fix:

When I disable a block component via /admin/structure/component, I can't enable it back again with an error message

Drupal\Component\Plugin\Exception\PluginNotFoundException: The "local_tasks_block" plugin does not exist.

.

… or rather, fixing this issue AFAICT should fix that bug.

I'm 95% confident that this is a duplicate of 📌 Capture all reasons why particular SDC is incompatible Active .

Why?

Because for the disabled SDC-sourced Components to be listed at /admin/structure/component/status, XB's decorated SDC plugin manager stores the necessary information in the State service under the \Drupal\experience_builder\Plugin\ComponentPluginManager::REASONS_STATE_KEY key.

To make Block-sourced Components also get listed at /admin/structure/component/status, it'll also need to end up being stored in that same key-value pair.

Conclusion: to make the UI treat both ComponentSources the same, the infrastructure needs to change. Which inevitably requires touching the same code paths.

P.S.: this likely will also require refactoring experience_builder_block_alter() away in favor of XB decorating the Block plugin manager (just like it does for the SDC plugin manager).

Merged into #3473275 and transfered issue credit: #3473275-6: Support disabled Block Components + multiple reasons for incompatibility → .