No Code Attached Yet
avatar Engholm
Engholm
18 Feb 2026

Steps to reproduce the issue

  • Create new custom fieldgroups and/or fields
  • create new language constants with language overrides for all each language
  • add language constants to custom field for title, description

Expected result

  • translated language text is shown in custom fields when editing articles, categories, user etc.
  • translated language text is shown in custom fields on overview grid of articles, categories, user etc.

Actual result

  • the text overrides are only shown inside editing articles, categories, users for the current language but the overview grids of the sections that support custom fields only show the the cryptic language constants (see attached screenshot)

System information (as much as possible)

Joomla 5 / 6 + PHP 8.4+

Additional comments

The language constants should be displayed throughout the backend with their assigned text translations. The only place where the language constants should be displayed is in the Language Overrides section.

Screenshot:
Image

avatar Engholm Engholm - open - 18 Feb 2026
avatar joomla-cms-bot joomla-cms-bot - change - 18 Feb 2026
Labels Added: No Code Attached Yet
avatar joomla-cms-bot joomla-cms-bot - labeled - 18 Feb 2026
avatar LSUDOKO
LSUDOKO - comment - 20 Feb 2026

hi @Engholm can you assign me this issue ??

avatar brianteeman
brianteeman - comment - 20 Feb 2026

we do not assign issues, anyone is welcome ro submit a pull request

avatar piyusshkumar
piyusshkumar - comment - 23 Feb 2026

Hi, @brianteeman @Engholm

I have reproduced this on 5.4-dev branch. Language overrides are applied correctly in the field edit form, but in the administrator Fields list view the raw constant is shown instead of the translated value.

Image

It looks like the list view is rendering the stored title directly without passing it through Text::_(), which causes the inconsistency.

Before preparing a patch, I’d like to confirm whether applying the translation in the View layer in HtmlView would be the preferred approach here or not.

If that’s acceptable, I can submit a PR.
Thanks.

Add a Comment

Login with GitHub to post a comment