Problem/Motivation
There are the things in the Add blocks page (Block library listing) which are block plugins. Those hold the description and the body. (for custom block, basic block type). Then there are other things on the Blocks admin listing. Those are block instances of those block plugins.
The dropdown buttons on the blocks in the UI on the site, inplace in the regions, have items in the dropbutton list. Some of those items deal with the block plugin: edit, delete. Some deal with the block (block instance): configure.
Also, on the block admin list, the dropbutton there on the admin list has items: configure, delete. *Those* deal with just the block instance. So it seems similar to the dropbottom that is inplace on the block there. This is confusing because it seems like you can do more from the inplace dropdown than in the admin list.
Both dropdowns have a delete, but the inplace delete deletes the plugin, not the block instance, the block admin list dropdown delete.
Proposed resolution
Make the dropbutton on the block admin list have the same things as the inplace dropbutton.
But.. make it clear that some of those effect just the row (which is the block instance) and some effect the block plugin (where the description comes from).
Add to the dropbutton: 'Edit plugin' and 'Delete plugin', optionally change the 'Delete' there to 'Delete block' and 'Configure' to 'Configure block'
Remaining tasks
- Discuss.
- Create initial patch to change the dropbutton.
- more tasks to come later...
User interface changes
Yes. Change the dropbutton on blocks in the block admin list.
API changes
No API changes.
Related Issues
- #1956496: inplace dropbutton on block instance needs to identify which action effect block (block instance) vs plugin (block library item)
- #1956504: Add block instance delete to inplace dropbutton on block instance
- #1956448: use the block instance title on the block admin listing
- #1956362: Name the page that lists block plugins, now: Blocks and Add Blocks, better: Block Library
- #1871746: Add block browser
- #1888702: Consider configuration selection instead of derivatives for most blocks
- #1535868: Change notice: Convert all blocks into plugins