I cannot find an example in the core, it happens when developing a third-party extension.
Whenever a field's value is JDEFAULT in the context of a menu item (while setting up a view), the translation is 'Home' (in English) rather than 'Default'.
Translation of JDEFAULT should be 'Default' (in English)
Translation of JDEFAULT is 'Home' (in English)
Any system supporting Joomla 4
joomla.ini and com_menus.ini have a conflicting language key JDEFAULT.
Shouldn't JDEFAULT be translated the same way throughout Joomla core?
Thanks Brian.
What I tried to convey is that I could not find an example of a menu item containing a field with value 'default' and translated with JDEFAULT where I could demonstrate the issue.
JDEFAULT has been added to com_menus.ini in Joomla 4.
It is such a global and general key, that any time JDEFAULT needs to be translated on a page where com_menus.ini is loaded, the translation will be 'Home' and not 'Default'.
It is such a global and general key, that any time JDEFAULT needs to be translated on a page where com_menus.ini is loaded, the translation will be 'Home' and not 'Default'.
The only time that com_menus.ini should be loaded is when in the menu component where it is the intended behaviour.
Status | New | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2022-09-23 18:41:38 |
Closed_By | ⇒ | alikon | |
Labels |
Added:
No Code Attached Yet
Removed: ? |
No. There are many examples of this - usually relating to permissions.