This thread is resolved. Here is a description of the problem and solution.
Problem: You are experiencing issues with translations resetting to a semi-translated state on your WordPress site using the Houzez theme, particularly after making changes in theme settings, adding Google reCAPTCHA, or updating the content in Elementor.
Solution: To address translation issues with theme options and Google reCAPTCHA fields: 1. Identify the fields you want to translate in the theme options, either by their label or by inspecting the element to find its "id" or "name". 2. Depending on the type of field: - For fields displayed with posts (like a metabox), go to WPML -> Settings -> Custom Field Translation. Set the field to "Copy" or "Translate", save, and then resave the content in the default language. - For fields that are just strings, go to String Translation -> Admin Strings, find and include the field, then translate it in String Translation. 3. For Google reCAPTCHA fields ('recaptha_site_key' and 'recaptha_secret_key'), include these in String Translation under 'houzes_options', correct the language settings if necessary, and translate.
Please note that this solution might be outdated or not applicable to your specific case. We highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the issue continues, please open a new support ticket at WPML support forum.
This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
Background of the issue:
I am trying to manage translations on my WordPress website using the Houzez theme. The issue occurs when I make changes in the theme settings, add Google reCAPTCHA to contact forms, or during theme updates. I edit the page in Elementor, save it, and afterward, the translation resets to a semi-translated state. I have tried to fix the translations multiple times without success.
Symptoms:
Translations on my WordPress website keep getting messed up randomly, especially after making changes in theme settings or adding editing and updating page in Elementor.
Questions:
Why do translations reset to a semi-translated state after making changes?
How can I prevent translations from getting messed up when updating the theme or editing with Elementor?
Apparently this sounds like something is creating a conflict. However, to understand the issue better can you please explain how you're translating the theme options and the pages? Usually theme options are not translated by just switching to another language from the top admin bar but you need to translate these in either WPML -> String Translation or have to set these fields to copy or translate.
Pages and Elementor stuff (i.e. templates, layouts) are translated using Advanced Translation Editor (ATE), or WordPress Editor in case you are not relying on ATE.
In short, if you can explain little more about the above mentioned, I can help you better regarding these issues.
Currently, everything I needed has been translated on the website, and everything is functioning normally. For now. Part of the translation was done using the Houzez theme options, while the rest was translated with the help of WPML.
However, many times in the past, I’ve experienced issues where, for example, after updating the theme, saving changes in the theme options, or adding an element to a page in Elementor, the translation "reverts" to some older state. As far as I can tell, the problem seems to occur with the translations made through the theme options, as this part of the translation "resets."
And then my only solution is to restore a backup, which is a problem because of the changes the client makes on the website.
In the previously sent attachments, you can see exactly what the problem is. The correct translation is in Serbian, but when the issue occurs, it ends up being a mix of English and Serbian.
Theme options can be a tricky business when translating. Usually we mistake these like regular content translations (i.e. translating posts and pages by clicking + icon or switching to another language).
For the theme options, if you try the following steps, I hope you'll not run into the said issues:
- Go to theme options and identify the fields you want to translate. This is usually guessed by the field label (i.e. field name is usually the same) or by inspecting the field element in browser to find its "id" or "name" parameter.
- Then there are 2 paths:
--- A) If these options are tend to display with each post (i.e. like a metabox to control the design, heading, sidebars or etc), then these are proper fields. In this case, you can:
------ go to WPML -> Settings -> Custom Field Translation section.
------ Search for the field and set it to "Copy" or "Translate" (depending on your need) and save.
------ After that, simply open the content having these fields for editing in default language and resave.
------ Usually if set to copy, the field values are copied to the translations, otherwise, you can update the translations and you should see these fields available for translation in the translation editor.
--- B) Sometimes these fields are just strings which you only need to translate to show as translated elsewhere (i.e. a few fields you showed in your screenshot). You can:
------ go to String Translation
------ and search for their content (or field names) and translate.
------ If nothing appears, then you scroll down to end of String Translation page and go to Admin Strings,
------ find the field there,
------ include in String Translation,
------ go back to String Translation,
------ search and translate.
However, in any case, if you run into the same problem again, I recommend isolating the issue by cloning the site into a staging/dev site and contact us, so we can investigate in detail. While, you can continue working on the live site.
Few times when i had this problem i tried to translate everything from theme options, Translations, again. And it looked fine until issue occurs, and then trasnlations were "reseted" to the same point of "mixed" translation. And every time issue occurs it "resets" translations to the same point.
Ok, I've watched the video and I am still convinced that those theme options are by default registered as English strings and are shown the same way. This is a common case among themes because usually themes are build this way or strings are registered as English by default, if there's no proper language tagged. This may also happen when WordPress is installed in English first but later you added WPML and chose a different language as default.
Anyways, can you please create a test or staging site, where this issue can be replicated? So I can investigate in more detail and can try to find a solution.
I've set your next reply as private to share the access safely.
Alternatively, you can use this sandbox site (hidden link one-click login). Here you can upload your theme and related plugins and reproduce the issue. I've configured WPML already.
Please let me know when you're ready.
P.S.: I'm just closing for the weekend and 'll be able to get back to you on Monday as earliest.
I was able to fix the issue by following the same method I did and described for other fields.
I included Google reCaptcha fields in String Translation:
- recaptha_site_key
- recaptha_secret_key
from "houzes_options", then corrected the language to Serbian and then translated to English. For English translation I used the same values.
Additionally I updated Elementor to the latest version.
And finally tested with enabling/disabling the reCaptcha in the contact form by editing in the Elementor.
Please watch my screencast hidden link for an understanding. The key points are:
- These options are stored as additional strings under "houzes_options" (i.e. [houzes_options]the_field_name).
- You can search in String Translation -> Admin Strings by using "the_field_name" part and then include in String Translation (if not included yet).
- Then search in String Translation.
--- Correct the language to "Serbian", in case if you see English flag with the string. This is important as mentioned earlier.
- Translate accordingly.
P.S.: During an initial test, I lost translation for those fields, so I used Google Translate to translate from Serbian to English, for a few "Contact Forms" fields. So you 'll need to:
- Correct translations.
- Translate again some options which were lost due to the issue.
- Replace Google reCaptcha keys with your own, as I used my test keys.
I see that the issue has been resolved, but only partially. The translations are still "messed up." I’ve already encountered a similar situation before, and I had to manually translate everything through the theme options. I’ve done this multiple times. Then, for no clear reason, the translations would "break" and end up in this same state—partially translated.
This problem has occurred during theme updates, sometimes while saving changes in the theme options, and most recently with editing the contact page.
If necessary, I can translate everything again, but I’m not confident the same issue won’t happen again, as it has occurred at least 25–30 times so far.
I can't understand what's happening, as the translations are fine until this kind of issue occurs.
And I see another problem now, plugin Latin now! that Converts Serbian Cyrillic characters into the Latin alphabet, does not convert strings you translated.
As of theme updates breaking changes, can you provide some steps to reproduce it or can demonstrate how it happens, with only WPML plugins and the said theme? So we can then look further into it.
However, the theme update breaking changes and the problem with Latin plugin are separate issues (than the ones originally reported here). I recommend opening a separate ticket because as per forum policy we can only handle one issue per ticket. So you can get more to the point help, without mixing up several issues in one long ticket.
I have found another solution to stop spam through the contact form, so I will not be using Google reCAPTCHA for now.
As for the issue with the "broken" translation, it’s difficult for me to replicate the error because it happens without any clear pattern. During one update, the issue appeared, but I restored a backup of the site, repeated the update, and everything went smoothly...
I will keep monitoring the situation and contact you again if necessary.
Regarding the Latin Now plugin, I wasn’t aware of any incompatibility since it works flawlessly on the live site.
