When i filter on my own (Dutch) language in the translation admin view it does not filter correctly. When i remove 'Not translated in' filter i see lots of strings not translated. But when i select Dutch from the options list it only shows a couple. I've had this problem for ages already but have always been too lazy to open an issue for it.
Steps to reproduce the Bug
not sure but this is a custom language i've added. Maybe that is the reason it is not working correctly.
Which Joomla version are you compiling in?
6.1.0
Which PHP version are you compiling in?
8.4
Which Joomla versions are you targeting?
6
Which PHP version are you targeting?
8.4
Which Web server is JCB running on?
apache/nginx
Which Relational Database is JCB running on?
mariadb 11.4
Which OS is JCB running on?
centos
Which JCB version are you using?
6.1.6 rc-1
Where in JCB did this issue occur?
Language Translations(admin_views)
On which browsers did you encounter the issue?
Firefox, Safari
Additional Comments
No response
### What Happened?
When i filter on my own (Dutch) language in the translation admin view it does not filter correctly. When i remove 'Not translated in' filter i see lots of strings not translated. But when i select Dutch from the options list it only shows a couple. I've had this problem for ages already but have always been too lazy to open an issue for it.
### Steps to reproduce the Bug
not sure but this is a custom language i've added. Maybe that is the reason it is not working correctly.
### Which Joomla version are you compiling in?
6.1.0
### Which PHP version are you compiling in?
8.4
### Which Joomla versions are you targeting?
6
### Which PHP version are you targeting?
8.4
### Which Web server is JCB running on?
apache/nginx
### Which Relational Database is JCB running on?
mariadb 11.4
### Which OS is JCB running on?
centos
### Which JCB version are you using?
6.1.6 rc-1
### Where in JCB did this issue occur?
Language Translations(admin_views)
### On which browsers did you encounter the issue?
Firefox, Safari
### Additional Comments
_No response_
Hi @TLWebdesign,
Thanks for reporting this issue. l’m still working to get to the root of the matter. As soon as I have a fix, I’ll let you know here in the issue.
Thanks once again for your patience and for taking time to report this issue.
Hi @TLWebdesign,
Thanks for reporting this issue. l’m still working to get to the root of the matter. As soon as I have a fix, I’ll let you know here in the issue.
Thanks once again for your patience and for taking time to report this issue.
@TLWebdesign, I found a temporary workaround for the issue. If you have access to your database, you can resolve it by updating the language_translations table so that any NULL values in the translation column are changed to an empty JSON object {}.
At the moment, records that have not been changed or saved at least once has NULL in this column, but the filter expects an empty JSON value in order to work correctly. Updating those values should allow the filter to behave as expected.
Please run the following SQL query on your Component Builder language translations table:
This is only a temporary fix. We will be implementing a more global and secure solution so that this works correctly for both fresh installations and existing setups going forward. But once the query has been applied, the filter should behave correctly.
@TLWebdesign, I found a temporary workaround for the issue. If you have access to your database, you can resolve it by updating the `language_translations` table so that any `NULL` values in the `translation` column are changed to an empty JSON object `{}`.
At the moment, records that have not been changed or saved at least once has `NULL` in this column, but the filter expects an empty JSON value in order to work correctly. Updating those values should allow the filter to behave as expected.
Please run the following SQL query on your Component Builder language translations table:
```sql
UPDATE `tableprefix_componentbuilder_language_translation`
SET `translation` = '{}'
WHERE `translation` IS NULL;
```
This is only a temporary fix. We will be implementing a more global and secure solution so that this works correctly for both fresh installations and existing setups going forward. But once the query has been applied, the filter should behave correctly.
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 i filter on my own (Dutch) language in the translation admin view it does not filter correctly. When i remove 'Not translated in' filter i see lots of strings not translated. But when i select Dutch from the options list it only shows a couple. I've had this problem for ages already but have always been too lazy to open an issue for it.
Steps to reproduce the Bug
not sure but this is a custom language i've added. Maybe that is the reason it is not working correctly.
Which Joomla version are you compiling in?
6.1.0
Which PHP version are you compiling in?
8.4
Which Joomla versions are you targeting?
6
Which PHP version are you targeting?
8.4
Which Web server is JCB running on?
apache/nginx
Which Relational Database is JCB running on?
mariadb 11.4
Which OS is JCB running on?
centos
Which JCB version are you using?
6.1.6 rc-1
Where in JCB did this issue occur?
Language Translations(admin_views)
On which browsers did you encounter the issue?
Firefox, Safari
Additional Comments
No response
Hi it's been two weeks without a response? 😅
Hi @TLWebdesign,
Thanks for reporting this issue. l’m still working to get to the root of the matter. As soon as I have a fix, I’ll let you know here in the issue.
Thanks once again for your patience and for taking time to report this issue.
Yeah no worries it's a low priority bug anyway. Was just curious if you were able to reproduce it.
@TLWebdesign, I found a temporary workaround for the issue. If you have access to your database, you can resolve it by updating the
language_translationstable so that anyNULLvalues in thetranslationcolumn are changed to an empty JSON object{}.At the moment, records that have not been changed or saved at least once has
NULLin this column, but the filter expects an empty JSON value in order to work correctly. Updating those values should allow the filter to behave as expected.Please run the following SQL query on your Component Builder language translations table:
This is only a temporary fix. We will be implementing a more global and secure solution so that this works correctly for both fresh installations and existing setups going forward. But once the query has been applied, the filter should behave correctly.