Background of the issue:
We have a website with the Houzez theme, and I had activated automatic translations during the setup of the website. Now it seems that things are translated without my knowledge, things that should not be translated at all, simply because they already are translated! For instance, in theme settings, there is a translation section, in which we can also rename labels. As the main language is Dutch, all should be Dutch. About a week ago, all of a sudden all was translated into Spanish. I reverted it, and now half is in English. Houzez support confirms it is caused by WPML. Apart from that, taxonomies are translated over again, and now it seems translation codes appear on the front end of the website.
Symptoms:
Unexpected automatic translations are occurring, causing issues with language consistency and translation codes appearing on the front end.
I just saw we used $ 55,03 in pay as you go. What??? How can that happen after switvhing off automatix translations?
Questions:
How can I switch off automatic translations in WPML?
Why are translations happening without my knowledge?
How can I ensure that certain sections remain in Dutch?
How can I fix the issue of translation codes appearing on the front end?
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
Hello,
Please take kindly note that credits are not refundable unless they were caused by a bug inside WPML.
According to our log 96064 credits were used. The jobs were for the post type "Properties".
Please verify the following:
I suggest you disable the automatic translation for "Properties" in WPML > Settings > Post Type Translation.
Even better, switch WPML > Translation Mode to "Translate what you choose".
This way nothing will be translated automatically in the background.
I can offer to take a closer look into the reported issue about the Houzez Theme Options. Would you be able to provide me access to a staging site for this purpose?
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
My apologies, but the provided access information that was provided on chat yesterday is today not longer available.
I would like to offer to have a closer look at the problem and request temporary access (wp-admin and FTP) to the website to investigate this issue further.
You can find the required fields below the comment section when you log in to leave the next reply. The information you provide is private, which means only you and I can see and access it.
IMPORTANT
Please be sure to make a backup copy of the website and database before allowing us access.
If you can't see the wp-admin / FTP fields, your post and website credentials are set as PUBLIC. DO NOT publish the data unless you see the required wp-admin / FTP fields.
I may have to install a plugin called "All In One WP Migration" to make a copy of the website where I can investigate the issue further.
However, I would also be very grateful if you could provide a staging site or copy of the website from your server yourself for this purpose. This step would only be required if the issue is replicable on such a staging site.
If you have any questions about creating such a staging site, you can consult your hosting provider. Just take note that WPML should be registered on this site again.
If you are unable to provide such a copy of the site for testing, please let me know on this ticket.
The private response form looks like this: hidden link
Next time you reply, click "I still need assistance."
Video: hidden link
Please note that we are obliged to request this information individually on each ticket. We may not access any access information not specifically submitted on this ticket in the private response form.
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
I have now implemented the workaround into the site. Please take note, that this usually should have been solved in WPML 4.5 but it might be that we are handling a regression.
Do I understand right, that the issue can be described like this?
"The result is that translations will not be displayed in the front-end and will revert to the admin's default language."
If so, please run a few tests and let me know if the issue occurs again. In case the workaround still solves the issue, we should then try to recreate the issue on a test site and escalate it internally.
The base language is Dutch. I have changed some of the labels that we didnt like, like for instance garage changed into parking space.
The first time, all those texts were translated/changed into Spanish. The second time, they were changed into English.
Is it possible that it has something to do with automatic translations? It is deactivated now, but it was active when that translation happened, and we will activate it again soon.
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
Hello,
I am sorry but I still do not fully understand.
The original strings are created in Dutch. Then you translate them with WPML String Translation into English and Spanish.
Is this correct?
If so, where exactly did the strings change unexpectedly?
1) On the original string
2) Or did the translations get mixed up?
I would like to provide a WPML test site on which you can install the latest version of the theme and we try to recreate the issue there. Would this be possible?
If we can recreate it, I can escalate it to our compatibility team and we can try to fix the issue and inform the Bricks Team about it.
The original strings are set in Dutch by Houzez. In the admin page "theme options" -> "translation" we have changed some of the strings, for instance, instead of garage we wanted parking place. Some other things that were badly translated from English by Houzez. But all still in Dutch.
all strings indeed later were translated through string translation in English, Spanish, German and french.
A week, maybe two weeks ago, suddenly, on that same page, a lot of the strings, such as bedrooms, bathrooms etc were translated into Spanish. Therefore, on the Dutch front end, those fields (field labels) suddenly were in Spanish. The translations madein string translations were still correct.
I changed all back to Ducth, so front end was correct.
Now, a couple of days ago, the same thing happened, but now in English. Not all strings, but quite a few. See screenshot. Like overview title, description title, they used to be in Dutch and now are in English.
Those are not strings that are used in properties or pages, so it cannot be that somebody translating a property or page accidentally translated these words.
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
Hello,
The workaround from the earlier suggested errata is already included in the latest version of WPML String Translation. It might be that this does not yet fully solve the issue.
Where you able to identify when exactly the issue occurs of how to trigger this unexpected behavior?
Possible Workaround, in case you would like to give it a try:
Register all the strings by default in English inside the theme options. Then translate them with WPML > String Translation.
I would like to provide a WPML test site on which you can install the latest version of the theme and we try to recreate the issue there. Would this be possible?
If we can recreate it, I can escalate it to our compatibility team and we can try to fix the issue and inform the Bricks Team about it.
Best regards
Andreas
The topic ‘[Closed] switch of automatic translations’ is closed to new replies.
