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
GitHub Issue #:
3410
Recent comments
The user fills a form on an Application node, that then flicks off emails, and responds with a Thanks page. Nothing too complex. Just that the deletion of the page providing the expected...
Problem upon submission
Please can you say more about the Rule? What does it do? Does it use any other Rule supporting modules? I presume if you disable the rule and create/save the node then you don't get the...
Problem upon submission
Yeah, so never mind. The issue arose because a page was deleted that had the URL-alias that the Rule was trying to redirect to. Maybe Core could have caught that the URL didn't exist, or...
Problem upon submission