Strange translations in the MAIN language

Just to let you know I had the same issue, starting November 22.
I also changed these texts manually. Indeed could be more texts that we didn’t notice..

Thank you for letting me know, Gabriel. I hope Translatepress fixes this soon. It is very strange bug.

I went back from version 2.4.2 to version 2.4.0 but unfortunately many main language (Dutch) strings are still corrupt. I hope that database is not corrupted.

Translatepress should NEVER change the main language. It is only for translations of the main language.

• This reply was modified 2 years, 3 months ago by gerske.

Hello there,

Thank you for letting us know about this!

We release this update because we had a problem regarding changing the default language from Settings -> General and probably this problem appears from there.

We already receive tickets about this and we are trying to solve this.

If there`s anything else, please let me know!

Kind Regards,

Translatepress is still very buggy at the moment.

Support asked me to drop _trp_gettext_* tables in the database and regenerate these tables. I did, but these strange translation in the main language still happen.

Support say they fixed it in the latest version, but it is clearly not fixed.

Please update Translatepress to a working version. We are losing many orders at the moment because of this behaviour.

Wondering when TranslatePress wil fix this problem. More and more users are reporting this problem here.

Yes Translatepress team, pleas let us know something. We relied on big project on your product, but right now we are kinda pissed off. Looks like a huge database shift problem. I am quite afraid of that…

I am having the same issue. I have temporarily deactivated translatepress on my site, but will follow this topic for resolution.

Translatepress is asking to get admin credentials to debug the situation and make a fix. Would anyone who is having this problem be able to give that to them? That would be of great help. There support is “TranslatePress Support” <[email protected]>.

I can’t give my access to them, and also I noticed that when I manually fixed some translations, they are messed again. This plugin is complete disaster ??

Does anyone know a way to keep other translations and remove only broken main translation? Tables are like below for example, and if main language is wpstg0_trp_gettext_de_de , when we delete this table only then plugin create new fresh one, but nothing works then. Plugin can’t find any strings in “Gettext string translations” for all languages and when I try to rescan I have “Plugins and theme scan did not finish due to an error”. All tables must be dropped.

wpstg0_trp_gettext_de_de
wpstg0_trp_gettext_en_us
wpstg0_trp_gettext_original_meta
wpstg0_trp_gettext_original_strings
wpstg0_trp_gettext_fr_fr

• This reply was modified 2 years, 3 months ago by elparts.

Hello there,

Try the latest version of TranslatePress which was released today and see if the issue is still there or not.

Also @elparts we don`t have a feature where you can keep the perfect strings and drop only the ones that have a problem.

Can you explain the behavior that you have there?

Let me know about this!

Kind Regards,

Nope, did not help at all.

Errore sul database di WordPress: [Illegal mix of collations (utf8mb4_unicode_520_ci,IMPLICIT) and (utf8mb4_unicode_ci,IMPLICIT) for operation '=']
INSERT INTO <code>wp_trp_original_strings</code> (original) SELECT DISTINCT ( BINARY t1.original ) FROM <code>wp_trp_dictionary_it_it_en_us</code> t1 LEFT JOIN <code>wp_trp_original_strings</code> t2 ON ( t2.original = t1.original AND t2.original = BINARY t1.original ) WHERE t2.original IS NULL AND t1.id > 0 AND t1.id <= 1000 AND LENGTH(t1.original) < 20000

{"action":"trp_update_database","trp_updb_action":"original_id_insert_166","trp_updb_lang":"de_DE","trp_updb_batch":0,"trp_updb_nonce":"792f119cb1","trp_update_completed":"no","progress_message":"fatto.<\/br><\/br>Inserting original strings for language de_DE..."}

I am getting this. This looks a SQL error, when trying to update the DB version!!!

I upgraded from 2.4.0 to 2.4.3 and switched on auto translation again. It has only been 1 day, but I didn’t see any strange changed in the main language strings. So far so good.

It seems to be ok on my site too. Good, it was really disaster before.