- Open on Drupal.org →Core: 9.5.x + Environment: PHP 7.4 & MySQL 5.7last update
about 1 year ago Waiting for branch to pass - 🇳🇿New Zealand RoSk0 Wellington
Ready for review now when 🐛 Store UUID for exportability Fixed is committed.
Taxonomy term referenced in "Select taxonomy term(s)" on the block configuration form should also be added as a dependency to the configuration object of that block.
See how happens with content blocks for example: when you create custom content block and place it in the region, configuration object for that block placement have a dependency entry like this:
langcode: en
status: true
dependencies:
content:
- 'block_content:basic:79af5eed-a1cb-4da7-aeec-56d650fb196d'
module:
- block_class
- block_content
- system
theme:
- sector_radix_starter
id: backtotop_2
Example above is from Sector configuration block.block.backtotop_2.yml.
- Create a term and a block
- Assign the block to display based on the presence of the term
- Delete the term
- View the block configuration form
Expected behaviour: dependency should prevent deletion of the required term.
Actual behaviour: term can be deleted, and this results in an error 500 when editing the block configuration; block config can no longer be edited via UI.
Add term from the configuration to the dependencies.
None
None
None
Needs review
2.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Ready for review now when 🐛 Store UUID for exportability Fixed is committed.