When new texts are used, the text to translate appears in Language Translation. When adding languages with + button, the default language is already entered but twice (see screenshot1.png).
When correcting all the option selection and clicking on 'save', the default language is selected twice again (see screenshot2.png).
After leaving the translation with close, the item is still with the flag "(no-translation)" (see screenshot3.png).
Steps to reproduce the Bug
Language translation -> open an untranslated item.
Which Joomla version are you compiling in?
5.4.2
Which PHP version are you compiling in?
8.3.23
Which Joomla versions are you targeting?
5.4.2
Which PHP version are you targeting?
8.3.23
Which Web server is JCB running on?
Apache 2.4
Which Relational Database is JCB running on?
MySQL 8.0.43-34
Which OS is JCB running on?
Linux
Which JCB version are you using?
5.1.4-beta4
Where in JCB did this issue occur?
Language Translations(admin_views)
On which browsers did you encounter the issue?
Safari
Additional Comments
No response
### What Happened?
When new texts are used, the text to translate appears in Language Translation. When adding languages with + button, the default language is already entered but twice (see screenshot1.png).
When correcting all the option selection and clicking on 'save', the default language is selected twice again (see screenshot2.png).
After leaving the translation with close, the item is still with the flag "(no-translation)" (see screenshot3.png).
### Steps to reproduce the Bug
Language translation -> open an untranslated item.
### Which Joomla version are you compiling in?
5.4.2
### Which PHP version are you compiling in?
8.3.23
### Which Joomla versions are you targeting?
5.4.2
### Which PHP version are you targeting?
8.3.23
### Which Web server is JCB running on?
Apache 2.4
### Which Relational Database is JCB running on?
MySQL 8.0.43-34
### Which OS is JCB running on?
Linux
### Which JCB version are you using?
5.1.4-beta4
### Where in JCB did this issue occur?
Language Translations(admin_views)
### On which browsers did you encounter the issue?
Safari
### Additional Comments
_No response_
@dormasta I'm unable to reproduce this issue on my end.
On my testing systems, I'm getting the following result:
I've also tested this on multiple environments, including fresh installations and existing setups, and the behavior is consistent across all of them.
With regards to:
After leaving the translation with close, the item is still with the flag "(no-translation)"
We will look into this, but it is not a critical issue at the moment. As mentioned, we are working on significantly improving the language area of JCB.
@dormasta I'm unable to reproduce this issue on my end.
On my testing systems, I'm getting the following result:

I've also tested this on multiple environments, including fresh installations and existing setups, and the behavior is consistent across all of them.
With regards to:
> After leaving the translation with close, the item is still with the flag "(no-translation)"
We will look into this, but it is not a critical issue at the moment. As mentioned, we are working on significantly improving the language area of JCB.
Hello Lemuel,
I now tried with the RC on Firefox, it is the same, I guess it is a language configuration issue between, Joomla languages, JCB languages and Browser languages.
Hello Lemuel,
I now tried with the RC on Firefox, it is the same, I guess it is a language configuration issue between, Joomla languages, JCB languages and Browser languages.
Hi @dormasta
Regarding the duplicate language loading, we discovered and fixed the bug.
After further, and deeper investigation, we identified that the issue was caused by an incorrect update to a custom language-related field I made during the alpha phase of 5.1.4.
This misconfiguration affected the filter logic, which resulted in:
Items still being marked as "not translated" even when translations existed
The default language being selected and displayed twice
Broken filtering when selecting "not translated in any language"
The root cause was an error in the custom code and field configuration within the language handling area, specifically related to the custom language field.
Unfortunately, this was not picked up at the time and only became apparent in more complex or upgraded environments.
My apologies for any inconvenience this may have caused.
This issue has now been fully resolved, and the fix will be included in the upcoming release. Thank you for reporting it and for your patience while we worked through the investigation.
Please let us know if you experience any further issues.
Hi @dormasta
Regarding the duplicate language loading, we discovered and fixed the bug.
After further, and deeper investigation, we identified that the issue was caused by an incorrect update to a custom language-related field I made during the alpha phase of 5.1.4.
This misconfiguration affected the filter logic, which resulted in:
* Items still being marked as "not translated" even when translations existed
* The default language being selected and displayed twice
* Broken filtering when selecting "not translated in any language"
The root cause was an error in the custom code and field configuration within the language handling area, specifically related to the custom language field.
Unfortunately, this was not picked up at the time and only became apparent in more complex or upgraded environments.
My apologies for any inconvenience this may have caused.
This issue has now been fully resolved, and the fix will be included in the upcoming release. Thank you for reporting it and for your patience while we worked through the investigation.
Please let us know if you experience any further issues.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
What Happened?
When new texts are used, the text to translate appears in Language Translation. When adding languages with + button, the default language is already entered but twice (see screenshot1.png).
When correcting all the option selection and clicking on 'save', the default language is selected twice again (see screenshot2.png).
After leaving the translation with close, the item is still with the flag "(no-translation)" (see screenshot3.png).
Steps to reproduce the Bug
Language translation -> open an untranslated item.
Which Joomla version are you compiling in?
5.4.2
Which PHP version are you compiling in?
8.3.23
Which Joomla versions are you targeting?
5.4.2
Which PHP version are you targeting?
8.3.23
Which Web server is JCB running on?
Apache 2.4
Which Relational Database is JCB running on?
MySQL 8.0.43-34
Which OS is JCB running on?
Linux
Which JCB version are you using?
5.1.4-beta4
Where in JCB did this issue occur?
Language Translations(admin_views)
On which browsers did you encounter the issue?
Safari
Additional Comments
No response
I will take a look at this, but please start using Firefox for JCB development or LibreWolf, since theses are the browsers I always use.
I tried FF, it is the same
@dormasta I'm unable to reproduce this issue on my end.
On my testing systems, I'm getting the following result:

I've also tested this on multiple environments, including fresh installations and existing setups, and the behavior is consistent across all of them.
With regards to:
We will look into this, but it is not a critical issue at the moment. As mentioned, we are working on significantly improving the language area of JCB.
Hello Lemuel,
I now tried with the RC on Firefox, it is the same, I guess it is a language configuration issue between, Joomla languages, JCB languages and Browser languages.
Hi @dormasta
Regarding the duplicate language loading, we discovered and fixed the bug.
After further, and deeper investigation, we identified that the issue was caused by an incorrect update to a custom language-related field I made during the alpha phase of 5.1.4.
This misconfiguration affected the filter logic, which resulted in:
The root cause was an error in the custom code and field configuration within the language handling area, specifically related to the custom language field.
Unfortunately, this was not picked up at the time and only became apparent in more complex or upgraded environments.
My apologies for any inconvenience this may have caused.
This issue has now been fully resolved, and the fix will be included in the upcoming release. Thank you for reporting it and for your patience while we worked through the investigation.
Please let us know if you experience any further issues.
Hello @dormasta,
Please let us know if the stable release has fixed this issue on your side as well so that we can go ahead and close this issue.