User tests: Successful: Unsuccessful:
— Collect overrides for all installed languages (per client) once per load and expose them to the overrides list view.
— Add two columns: Translated (per-language badges for existing overrides) and Not translated (badges to create missing overrides), showing language codes with quick edit/create links.
— Prefill the add form with the source constant/text when creating a missing override via a badge, while preserving filter context on redirects.
index.php?option=com_languages&view=overrides, pick a language/client; ensure the Translated and Not translated columns appear.Documentation link for docs.joomla.org: Happy to provide a documentation when merged!
[] No documentation changes for docs.joomla.org needed
Pull Request link for manual.joomla.org:
No documentation changes for manual.joomla.org needed
| Status | New | ⇒ | Pending |
| Category | ⇒ | Administration com_languages Language & Strings |
| Title |
|
||||||
| Labels |
Added:
Language Change
PR-6.1-dev
|
||
I find the use of the terms Translated/Not Translated confusing as the strings are translated they are just not overriden
yes first I used "Associations", but they are not "Associations", so I thought Translated / Not Translated, because in fact if the language keys do not exist in another ini because they are used "custom" they are not translated then. For example you could insert FIELDS_LABEL_TEST into a Fields label and then create language overrides for it.
will check the codestyle!
I have tested this item ✅ successfully on 81aebe2
tested successfully with 3 languages for Site and Administrator
I find the use of the terms Translated/Not Translated confusing as the strings are translated they are just not overriden
yes first I used "Associations", but they are not "Associations", so I thought Translated / Not Translated, because in fact if the language keys do not exist in another ini because they are used "custom" they are not translated then. For example you could insert FIELDS_LABEL_TEST into a Fields label and then create language overrides for it.
but if they do exist then they are already translated they are just not overriden/customised
i do see this as a useful improvement
I find the use of the terms Translated/Not Translated confusing as the strings are translated they are just not overriden
yes first I used "Associations", but they are not "Associations", so I thought Translated / Not Translated, because in fact if the language keys do not exist in another ini because they are used "custom" they are not translated then. For example you could insert FIELDS_LABEL_TEST into a Fields label and then create language overrides for it.
but if they do exist then they are already translated they are just not overriden/customised
What about Existing Override / Not Existing Override ? It's a bit long but no other idea right now
Sorry for the wrong Commit Message. The table header are now "Override" and "No Override".
| Title |
|
||||||
I find the use of the terms Translated/Not Translated confusing as the strings are translated they are just not overriden