-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[UX] Menu link items should be kept in sync with their respective content titles #4759
Comments
...I wasn't sure if this is a feature or a bug, but the behavior as it currently is feels like a UX WFT to me, so I've tagged this as a bug for now. |
I get your point, but a word of warning here: I'd not recommend to force content title and menu item to be synced. Often they differ by intention. And I'm not sure if the same logic as in pathauto should get applied. This might need more feedback. And it's not a bug. 😉 |
In Backdrop, we've included the functionality of https://www.drupal.org/project/pathauto_persist (which is what I'm suggesting we do here as well). Try the following:
What I'm proposing is to basically allow the same flexibility with menu items linked to content. The way this will work will cover both cases of keeping the menu in sync or not. Consider these scenarios:
|
I agree that this can be annoying for some users, while others expect it to work this way. I support giving users a choice as to whether or not titles/menu items are synced on a per-node basis. I like @klonos' "expected behaviour" scenario. I also agree with @indigoxela that this isn't a bug, its by design (its just a bad design for some users). So this should be a feature request to make that 'design' optional. |
Fair enough 👍 |
Many thanks for the detailed example. Makes sense. Another question: what if the acting user does not have permission to add a menu item. Should the menu item still get created / synced then? I'm thinking of the contrib module auto_menu_settings, which provides automatic menu items for less privileged users and also can hide all the settings. But maybe that's going beyond the purpose of this issue. 😉 |
It is, but this has been raised before. Not sure if we have just discussed it during a meeting, or in #1610, can't find an issue for it 🤔 |
...aha: #901 |
This happens for content types that have the "Add a link into the menu for new content of this type" option enabled (menu settings):
Actual behavior
The page gets renamed to "Renamed page", but the respective menu item remains "Page"
If you edit the page, the breadcrumb shows the old name (expected, since breadcrumbs pick parts from the menu items), which is confusing:
Expected behavior
Things work the same way as the "Generate automatic URL alias" checkbox works (pathauto "persist" feature):
When the "Provide a menu link" option is enabled for the node, there is another "Update menu title when the content title changes" checkbox. When that second checkbox is ticked, the "Menu link title" field is disabled:
The menu item title is synced with the content title. Renaming the content also renames the menu item.
If the user wants to "break the sync" between the menu item title and the content title, they need to untick that second checkbox.
Alternatives
The text was updated successfully, but these errors were encountered: