You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the model PageContent offers a flag in_navigation, which means that in a multi-language setup, it is possible to create different navigation menus depending on the language. This to users is quite confusing, because one would assume that the menu structure should be independent of the language.
It moreover makes it even more confusing if versioning is enabled, because then that flag is versioned. We for instance had to disable the button "Show in Menu", because versioning and showing/hiding from navigation just doesn't fit. Please check #7780 for details.
Shall flag in_navigation be moved from model PageContent to Page?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Currently the model
PageContent
offers a flagin_navigation
, which means that in a multi-language setup, it is possible to create different navigation menus depending on the language. This to users is quite confusing, because one would assume that the menu structure should be independent of the language.It moreover makes it even more confusing if versioning is enabled, because then that flag is versioned. We for instance had to disable the button "Show in Menu", because versioning and showing/hiding from navigation just doesn't fit. Please check #7780 for details.
2 votes ·
Beta Was this translation helpful? Give feedback.
All reactions