Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
What are the advantages in using this module compared to adding per-language path aliases?
Comments
Comment #1
rvilarWith Drupal menu system, you only can add a real path in one menu (it's a core limitation). When we are developing an i18n website, normally, we have different menus for each language. Making per-language path aliases don't solve this problem because, Drupal menu system saves the real path nor the aliases. This can break the breadcrumb, menu_block, etc.
With this module, you've one real path for each language.
Comment #2
miro_dietikerYou would even have the capability to set the active menu handler on a custom code basis and thus aliases might work.
(Menu items with language are more specific and thus are subject of higher match priority than language free items.)
Note that we initiated an extension where drupal (i18n) considers the menu item language when deciding its active state. Thus, your argumentation of need would be obsoleted: Aliases and menu items have a language that can be interpreted correctly in priorities.
If there's even more why you state we need it, please tell me.
Comment #3
fastangel CreditAttribution: fastangel commentedDo you need more information?. Do we can close issue?