Eduardo Larequi

Thank you very much for the fix, @wordpressslider.

The problem has not been resolved. The latest version reported by WordPress is 2.9.1, but the version on www.ads-software.com is 2.8.5. Another bug?

• This reply was modified 5 years, 1 month ago by Eduardo Larequi.

I was right: https://www.ads-software.com/support/topic/latest-version-2-9-0/

In all my WordPress sites where Elementor is installed, the update function indicates that there is an update of Elementor (version 2.9.0), ready to be downloaded and installed. However, If I click the “Download” button in WordPress plugin repository, I get version 2.8.5. On the other hand, version 2.9.0 can be downloaded from the repo if you know its URL.

Can anybody explain this discrepancy? Under these circumstances, I am not sure if I should update Elementor (version 2.8.5). Judging from some previous experiences, it seems as if Elementor 2.9.0 had been removed from the repository.

Am I right, or not? Is the update safe?

I’m not sure if someone has opened a ticket on this issue. The problem with Atomic Blocks and other plugin translations is not due to a bug, but to a lack of attention to the complexity of translating the new WordPress editor.

Anuway, thank you very much for your attention, David.

WordPress 5.0 has added a new system, based on JSON files, to translate the text strings which appear in the new WordPress editor (Gutenberg). Although it applies to Genesis Framework (a theme), you can see an thorough explanation here: https://studiopress.community/topic/new-genesis-sidebar-in-wordpress-5-x-editor-is-not-translated/. The situation is a bit different from the one you describe in your post, but the basis of the problem is the same.

Even though you fully translate the .PO file and upload the translation files to WordPress, most of the plugin remains untranslated, because of the lack of the JSON files.

Trying to find a solution, I’ve generated the JSON files from the atomic-blocks-es_ES.po file, as it is explained in the link above (the wp-cli command generates more than 60 different files), and then I have uploaded them to WordPress, but it doesn’t work.

This new WordPress translation system is not easy to understand, and I’m afraid that many plugin developers are not applying it in their code. In my humble opinion, the problem is very serious, because there is a growing number of plugins which interact with new WordPress editor, and also a growing number of text chains which remain untranslated because of the lack of the appropiate JSON files. The consequence of this situation is very ugly: after installing two or three plugins which interact with WordPress editor, you get an unpredictable mixture of spanish and english.

By the way, David, if you feel more comforable talking about this issue in spanish, you can send me a message through the contact form of my web site: https://www.labitacoradeltigre.com/formulario-de-contacto/. I will answer by email.

Version 2.9.1 works nice. Thank you very much, Paul.

Thanks for the information, James.

In versión 7.1.1 Jetpack blocks remain untranslated.

Thanks four your attention and interest, @macmanx.

I run WordPress 5.1 in all my sites.

I upload my own translations because I don’t like some aspects of the “official” ones. GlotPress is a very good way of making collaborative translations, but at the same time we should admit that the quality of many of them is, to put it politely, quite questionable.

Anyway, I do not want to criticize the efforts of the community, which I respect and admire. I only want to understand the mechanisms of the new translation system, as described here, https://make.www.ads-software.com/core/2018/11/09/new-javascript-i18n-support-in-wordpress/, and use it for my own particular needs.

As for Jetpack, apart from the “official” .po and .mo files, which are downloaded automatically to /wp-content/languages/folder when user clicks the Update button, there is a /wp-content/plugins/jetpack/languages/json/ folder, which contains the translation .json files necessary for translating Jetpack admin pages. In other words: .po and .mo files are a necessary, but not a sufficient condition for translating Jetpack.

My question is very simple: if Jetpack is fully translated to Spanish in GlotPress (and it is), why Jetpack blocks are not translated, even after updating all translation files? And this is only a part of the problem: as I have said before, many plugins which add blocks to Gutenberg editor lack appropriate translations for them. In some cases, these translations only translate admin pages, but not the name and the options of the blocks.

In my humble opinion, the correct and thorough translation of non native Gutenberg blocks is a crucial point in the development and success of the new edition interface established by WordPress 5.0. I like Gutenberg very much and I don’t have any personal problem with texts in English, but at the same time I consider the current lack of translations for many, many blocks, a very serious problem for those users who feel uncomfortable with English words.

In addition to about 12 personal sites (most of them are test sites), I manage more than 190 sites for schools in Navarre, Spain, and I feel very worried about the current situation. Until version 5.0, I was able to modify standard translations when I needed it, by means of custom .po and .mo files; now I do not know how to get proper and thorough translations.

• This reply was modified 6 years ago by Eduardo Larequi.

Hi @richtabor,

I have not submitted my Spanish translation to WordPress, due to some partiocular reasons. One om them, but not the only one, is that I want to check the quality of the translation in a real context, that is to say, in a new site I’m working on with Block Gallery plugin and other block collection plugins for Gutenberg (by the way, none of them contains the JSON translation files, which poses the same problems as the translation of Block Gallery).

On the other hand, I do not know how to find “the md5 of the relative path of each file”. Is there a simple way to get it? And which file should I select to find its md5, the JSON file in WordPress servers, the main file of the plugin, another one? If I have to get the md5 of the JSON file, this is a vicious circle, because it does not exist yet.

Finally, after reading carefully this article https://pascalbirchler.com/internationalization-in-wordpress-5-0/, I have found that the ${domain}-${locale}-${md5}.json file name is not the only possible one. As far as I can understand (English is not my first language), I think I could use another name for the translation file, and put it in the plugin /languages folder, as long as it is in the following form: $textdomain-$locale-$handle.json. Applying this form, the translation JSON name file would be “block-gallery-es_ES-block-gallery-editor.json”.

My question is the following: is “block-gallery-es_ES-block-gallery-editor.json” a correct name for my translation file? I am pretty sure it is not (or I am doing something wrong with it), as I have tried it several times, with no success at all.

Anyway, thank you for your suggestions and your excellent plugin.

I’ve just solved my problem, by deactivating the plugin, removing all authLDAPOptions options in WP database and activating the plugin again from network menu, as suggested in https://github.com/heiglandreas/authLdap/issues/140.

Quite tricky, but it works!

Spanish translation works fine with the new translation files. Here you have the .PO and .MO files.

Thank you very much, @indrek_k, for your plugin and your attention.

Thank you, @indrek_k, for your solution. I’ll be waiting for the new release.