[#48686] - [6.2] Fix language overrides consistency in tags, fields, and user groups (#48651)
- Closed
- 22 Oct 2026
- Medium
- Build: 6.2-dev
- # 48686
- Diff
- Devansh-dvd:fix-48651-language-overrides-consistency
User tests: Successful: Unsuccessful:
Pull Request resolves #48651.
- I read the Generative AI policy and my contribution is either not created with the help of AI or is compatible with the policy and GNU/GPL 2 or later.
Summary of Changes
In Joomla core, several components support language constants for item titles so that multilingual sites can translate dynamic titles using Joomla's Language Overrides. For example:
- In
com_workflow(workflows/default.php), titles are wrapped withText::_($item->title). - In
com_menus(ItemsModel.php), titles are parsed throughText::_($item->title).
However, across several other administrator list views, item titles were output directly to the template with <?php echo $this->escape($item->title); ?> without passing through Text::_(). As reported in #48651, this causes language constants to fail to translate and display raw unformatted strings (e.g. TAG_SPECIAL_OFFERS) in the admin tables.
This PR wraps item titles and checkbox grid.id attributes with Text::_() across:
- Tags List:
administrator/components/com_tags/tmpl/tags/default.php - User Groups List:
administrator/components/com_users/tmpl/groups/default.php - Access Levels List:
administrator/components/com_users/tmpl/levels/default.php - Custom Fields List:
administrator/components/com_fields/tmpl/fields/default.php - Field Groups List:
administrator/components/com_fields/tmpl/groups/default.php
Testing Instructions
-
Turn on Debug System and Debug Language:
- Navigate to System → Global Configuration → System tab.
- Set Debug System =
Yesand Debug Language =Yes. - Click Save & Close.
-
Create a test Language Override:
- Navigate to System → Manage → Language Overrides.
- Select English (United Kingdom) - Administrator.
- Click New.
- Constant:
TAG_SPECIAL_OFFERS - Text:
Special Deals & Offers - Check For Both Locations and click Save & Close.
-
Create a Tag with a Language Constant:
- Navigate to Components → Tags.
- Click New.
- Title:
TAG_SPECIAL_OFFERS - Click Save & Close.
-
Inspect the Tags List table (
administrator/index.php?option=com_tags&view=tags). -
Also inspect the User Groups table (
administrator/index.php?option=com_users&view=groups).
Link to documentations
Please select:
-
Documentation link for guide.joomla.org:
-
No documentation changes for guide.joomla.org needed
-
Pull Request link for manual.joomla.org:
-
No documentation changes for manual.joomla.org needed
| Status | New | ⇒ | Pending |
joomla-cms-bot
- | Category | ⇒ | Administration com_fields com_tags com_users |
| Title |
|
||||||
@brianteeman i updated the title to [6.2] . Please check out
Thanks for correcting the title of the PR
If I understand you correctly the intention is to allow the use of Language constants for things such as tags and fields. In your original issue you said that this was a regression (change in behaviour) from Joomla 5. Are you now not saying that?
The problem I see with the current PR is that it only addresses the use of a language constant in a few places - for example if I use a constand for a tag name then it is displayed as you wish in the tags manager but does not display correctly in the list of tags to select from in an article
Thats just an example - the same is true for all the other changes you have made
For tags it also creates a problem is that the alias for the tag is generated from the title which in this case is a constant and not a string
And on the front end of the site it doesnt work at all as you didnt make the same changes for the way it is displayed there
In short I can see what you are trying to do but it is incomplete and I am not sure if it is something we actually want but thats for maintainers to decide not me
Thanks for correcting the title of the PR
If I understand you correctly the intention is to allow the use of Language constants for things such as tags and fields. In your original issue you said that this was a regression (change in behaviour) from Joomla 5. Are you now not saying that?
The problem I see with the current PR is that it only addresses the use of a language constant in a few places - for example if I use a constant for a tag name then it is displayed as you wish in the tags manager but does not display correctly in the list of tags to select from in an article
Thats just an example - the same is true for all the other changes you have made
For tags it also creates a problem is that the alias for the tag is generated from the title which in this case is a constant and not a string
And on the front end of the site it doesnt work at all as you didnt make the same changes for the way it is displayed there
In short I can see what you are trying to do but it is incomplete and I am not sure if it is something we actually want but thats for maintainers to decide not me
Thanks for correcting the title of the PR
If I understand you correctly the intention is to allow the use of Language constants for things such as tags and fields. In your original issue you said that this was a regression (change in behaviour) from Joomla 5. Are you now not saying that?
The problem I see with the current PR is that it only addresses the use of a language constant in a few places - for example if I use a constant for a tag name then it is displayed as you wish in the tags manager but does not display correctly in the list of tags to select from in an article
Thats just an example - the same is true for all the other changes you have made
For tags it also creates a problem in that the alias for the tag is generated from the title which in this case is a constant and not a string
And on the front end of the site it doesnt work at all as you didnt make the same changes for the way it is displayed there
In short I can see what you are trying to do but it is incomplete and I am not sure if it is something we actually want but thats for maintainers to decide not me
I have tested this item 🔴 unsuccessfully on 9ca5c8c
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/48686.
I have tested this item 🔴 unsuccessfully on 9ca5c8c
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/48686.
Thank you @brianteeman for taking the time to test this so thoroughly and pointing out those additional touchpoints!
When testing on a clean install, I confirmed that Joomla has never supported language constants in these title fields out of the box. I should have classified this as a proposed feature request rather than a regression from 5.x.
I went through your points deeply
- Scope: Wrapping the titles in
Text::_()inside the list managers was an initial step, but as your screenshots clearly show, it leaves out the article tag selection field (TagField), the frontend article tags layout (layouts/joomla/content/tags.php), and similar custom field layouts. - Aliases: Because the alias is generated from the title, using a constant results in slugs like
tag-special-offersrather than human-readable words. - Architecture: Since Joomla already provides a robust Multilingual Associations system (creating separate items per language and linking them), allowing database titles to be raw language constants might conflict with the intended architectural design of Joomla's multilingual workflow.
Given this, I would appreciate the maintainers' guidance: Is supporting language constants in titles across all forms and frontend views a direction Joomla wants to take, or should this be closed in favor of using Joomla's existing Multilingual Associations feature?
Thank you again for the detailed review and guidance!
Thank you @brianteeman for taking the time to test this so thoroughly and pointing out those additional touchpoints!
When testing on a clean install, I confirmed that Joomla has never supported language constants in these title fields out of the box. I should have classified this as a proposed feature request rather than a regression from 5.x.
I went through your points :
- Scope: Wrapping the titles in
Text::_()inside the list managers was an initial step, but as your screenshots clearly show, it leaves out the article tag selection field (TagField), the frontend article tags layout (layouts/joomla/content/tags.php), and similar custom field layouts. - Aliases: Because the alias is generated from the title, using a constant results in slugs like
tag-special-offersrather than human-readable words. - Architecture: Since Joomla already provides a robust Multilingual Associations system (creating separate items per language and linking them), allowing database titles to be raw language constants might conflict with the intended architectural design of Joomla's multilingual workflow.
Given this, I would appreciate the maintainers' guidance: Is supporting language constants in titles across all forms and frontend views a direction Joomla wants to take, or should this be closed in favor of using Joomla's existing Multilingual Associations feature?
Thank you again for the detailed review and guidance!
Yep, I’ll close this PR and open a feature discussion instead so I can discuss the idea with the maintainers and get their feedback before proceeding.
| Status | Pending | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2026-10-22 20:03:38 |
| Closed_By | ⇒ | Devansh-dvd | |
| Labels |
Added:
PR-6.2-dev
|
||
The title of the pr says 5.4 but it has been made (correctly) on the 6.2 branch so please could you correct the title here on github