This thread is resolved. Here is a description of the problem and solution.
Problem: When using the Houzez theme with WPML, a new coworker adds properties in English, but encounters issues where the backend is partially in Dutch, and custom fields in the classic translator show up in Dutch instead of English, despite being translated through string translation. Solution: We recommend setting the theme’s Fields Builder custom fields (like select, dropdown, multiselect) to “Copy” and translating their labels via WPML → String Translation. Here’s how to configure this: 1. Navigate to WPML → Settings → Custom Fields Translation 2. Click Show system fields 3. Find the custom fields that appear in the original language in the translation editor 4. Set them to Copy 5. Save the changes Afterwards, edit a property in the original language, make a small change, update the page, and then complete the translation in the translation editor. This setup should correct the language display issues in the translation editor.
If this solution does not resolve your issue, or if it seems outdated, 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 problems persist, 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.
we use the houzez theme together with wpml. we used to create properties in dutch, and then translate into the other four languages.
now, a new coworker adds properties in english, but there are several problems. first, her backend is half dutch, but that might possibkly be fixed by string translation. worse is that in the classic translator, strings that in the backend and the property clearly show up in english, appear in dutch in the translation editor and the translations are not shown, even though all options are already translated through string translation.
that does only happen to the theme's custom fields, the taxonomies are well translated.
Are the Properties stored as custom fields, or are they taxonomies?
Also, have you considered (also testing) keeping all properties in one language first and then translating them afterward? This might avoid inconsistencies.
Regarding this part:
worse is that in the classic translator, strings that in the backend and the property clearly show up in english, appear in dutch in the translation editor and the translations are not shown, even though all options are already translated through string translation.
that does only happen to the theme's custom fields, the taxonomies are well translated.
It would be very helpful if you could provide more details and upload additional screenshots highlighting what is wrong with each, as well as how the properties are added and translated (including any other related settings).
as said earlier, we use Houzez. Properties are custom post types.
we used to enter all properties in dutch and then translate. now we have a new collegue, who does not speak dutch, so she does have to enter in english. that should not be any problem, right?
What happens?
we go to properties - new property
the first part is title and description as usual. the second part is the standard houzez fields. they are mostly in dutch - which should be english. taxonomies, like property type, city, are fine, all english, as are features, all translated by the string translations. the last part is the custom fileds, created by us, where field names and values are english - perfect.
now we go to the translations.
the upper part, description, title, taxonomies and stanard houzez fields are fine, displayed in english at the left side ("original language which is english, as the property is entered in english) and the values - when already translated, like the taxonomies, are already translated just to be approved. but the bottom part, the custom fields are wrong. at the left side, the original language part, the values are shown in dutch - weird as that should be english, and therefore all values are empty to be filled in. also weird, as all are already translated through string translation.
another issue appeared today. i made some changes to the hompage and then updated the translations. even though all fields are translated, the translations are not completed, appear as pending, stating "translatyion assigned to a local translator".but it is already translated!
I need to request temporary access (wp-admin and FTP) to your site—preferably to a test site where the problem has been replicated if possible—in order to be of better help. When you log in to leave your next reply, you will find the needed fields below the comment area. The information you will enter is private, meaning only you and I can see and access it.
I’ve looked into this, and the situation is a bit tricky because of how your current theme handles it. Let me explain:
1. You mentioned that properties are starting to be added in English, which is fine. However, part of the backend appears in Dutch. This happens because translations have been set in Theme Options → Translation. Even if some strings are translated via WPML → String Translation, the theme settings override them with the values defined in the theme options. This behavior is likely intended for setups that do not use translation plugins.
In this case, I would recommend removing the translations from the theme options and leaving those fields empty. Then, manage all frontend translations through String Translation if necessary.
2. Regarding the custom fields created via the theme’s Fields Builder, this is also related to how the theme implements this. The values are added in Dutch in the theme options, which is why they appear in the translation editor as default values (even if the original property is in English).
However, from what I can see, the frontend still displays the correct translated values from String Translation, as expected.
I recommended making a full backup before any changes or testing first on the staging site.
those are not so much translations, as an opportunity to change standard texts. For instance, we did change property size to Built, and land area to plot size.
houzez states on its website that it is wpml compatible, but giving above comments, is that really true?
the website does have daily backups, so please have a look to see how to solve ther issues.
also please have a look at the homepage translations, i do not know why they are not processed as completed, and therefore changes made in dutch are still not visible in the other languages.
New threads created by Andrey and linked to this one are listed below:
Yes, the Houzez theme is compatible with WPML, and from what I can see, your site is functioning correctly in a multilingual context on the frontend.
However, even though you have changed some of the default texts, other parts still appear in Dutch. This is because strings are still being pulled from the theme option translation, which is why you’re seeing a mix of languages.
also please have a look at the homepage translations, i do not know why they are not processed as completed, and therefore changes made in dutch are still not visible in the other languages.
Could you please provide more details about the recent changes made to the homepage? If further checking is needed, I would like to ask for your permission to replicate your site locally. For this, I would temporarily install a plugin such as Duplicator or All-in-One WP Migration to create a full copy of your site and its content.
Hi, i still think it is very strange and should not be correct, that a wpml compatible theme shows a mix of languages in the backend. that makes it impossible to work with for international teams, one of the targets for multilingual websites.
about the homepage: in Dutch, an employee is added in the "about us" section. So in Dutch there are four, in the other languages still three.
Hi, i still think it is very strange and should not be correct, that a wpml compatible theme shows a mix of languages in the backend. that makes it impossible to work with for international teams, one of the targets for multilingual websites.
As I mentioned before, I would recommend first removing all the translations from the Theme Options → Translation and adding the necessary ones in WPML → String Translation.
about the homepage: in Dutch, an employee is added in the "about us" section. So in Dutch there are four, in the other languages still three.
well, removing those would still not explain why the custom fields are not translated.
according to your comments, that is because of the weay houzez handles it, so in my opinion, that m,eans houzez is not 100% compatible, as the gtranslator should always show the correct language. if not, its impossible to translate.
I installed your site locally, ran several tests, and also checked this with our compatibility team.
Regarding the theme’s Fields Builder custom fields (such as select, dropdown, multiselect — fields where you choose one or multiple values from a list), these must be set to “Copy”. Their labels should be translated via WPML → String Translation.
This is the expected setup for compatibility with the Houzez theme. When configured this way:
• The field values are copied correctly to translations
• They will no longer appear in the translation editor in the wrong language
• The labels remain translatable via String Translation
Steps to configure this:
1. Go to WPML → Settings → Custom Fields Translation
2. Click Show system fields
3. Locate the relevant custom fields that appear in the translation editor in the original language
4. Set them to Copy
5. Save the changes
After that:
• Edit a property in the original language (e.g., English)
• Make a small change and update the page
• Open the translation editor and complete the translation
This should ensure everything syncs and displays correctly.
