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
I agree with @yorkshirepudding for new sites. Existing sites that use this "long text with summary" functionality already... not sure. There is an old core issue around this, too, it looks...
Use text editors in Summary Field
I always do a separate summary field for these reasons: Avoids the UI cludge of having either a summary or a trimmed value of body Allows summary to be mandatory...
Use text editors in Summary Field
It seems that while the summary field does not have a WYSIWYG editor. It does have the same text format as the main body field. Cutting and pasting content from the body field does not...
Use text editors in Summary Field