Say for whatever reason, a site builder needs to replace a menu with another via the admin UI, while at the same time retaining the configuration (menu style and depth, style settings, visibility conditions):
- Add a new menu block in the same region.
- [add as many steps/clicks here as required to manually copy the configuration of the old menu block...]
...
n-2. ... n-1. Remove the old menu block n. Save the layout
...so basically the more complicated configuration the old menu block has, the more clicking a site builder needs to do in order to replicate the block configuration to the new menu block.
Compare the above to this:
- Edit existing menu block.
- Select another menu from a drop-down menu that lists all available menus.
- Save the menu block
- Save the layout
Recent comments
https://www.drupal.org/project/views/issues/1266388 shows that this is an architectural issue, and requires another 2 hooks being adjusted. It would be really nice to add comments/notes to...
node access
Hmmm, from D7 ancient tomes: from https://drupal.stackexchange.com/questions/7056/limit-which-roles-can-view-a-node-basing-on-its-content-type yet https://docs.backdropcms.org/api/...
node access
I also note on this screen: "Furthermore note that content which is not published is treated in a different way by Backdrop: it can be viewed only by its author or users with the...
node access