“blocksy-dashboard-scripts” strings do not appear translated

Hello @itapress,

Actually, we are already loading the translations in the admin_enqueue_scripts action from the plugin.php. You can see there that we add the translations to the blocksy-companion domain with the wp.i18n.setLocaleData(...) call.

I just tested now the Polish translation from wp.org and everything appears to be translation in the dashboard: https://share.cleanshot.com/6SFKSwMF

If some translation doesn’t appear on your end, it’s better to let us know which language you are testing with and which string specifically doesn’t get translated (ideally, by providing a screenshot).

Thanks a lot!

Looking forward to hear back from you.

Best,
Andrei

Hello @creativethemeshq

Thank you for the reply.

I would like to point out that I deal with WordPress translations for the Italian language and that I would like to contribute and help to improve the management of translations of this plugin.

Unfortunately, for my language there is not a complete translation on translate.www.ads-software.com and therefore I am carrying out the tests with the Dutch language which instead is 100% complete.

Here are the links to the screenshots of the “before” and “after” of the changes I proposed and which essentially concern that the translation strings (in my example in Dutch) for the files relating to “blocksy-dashboard-scripts” are taken from those generated by translate.www.ads-software.com and which are automatically loaded at the path /wp-content/languages/plugins/

Message that appears when the Blocksy theme is not activated:

Before: https://snipboard.io/BlQzVu.jpg

After: https://snipboard.io/TRfdzL.jpg

Extensions tab that appears when the Blocksy theme is activated:

Before: https://snipboard.io/byO0uf.jpg

After: https://snipboard.io/AIl7JS.jpg

Best regards.

@itapress Thanks a lot, I have managed to reproduce this issue. Will take a closer look into our enqueueing of the JED locale data and will get back to you.

It looks like this past updates + changes in WP 6.5 broke something in our usual process.