This thread is resolved. Here is a description of the problem and solution.
Problem:
The client was trying to translate permalinks slugs for the custom taxonomies set from the Houzez theme but encountered issues where the expected translated slugs were not appearing, and instead, the original language slug was still being used. Additionally, the client faced 404 errors on the translated pages.
Solution:
Note: While using the theme Houzez, make sure that you translate the custom taxonomies that come with the theme only from the page: WPML -> Settings -> Taxonomies Translation section (all the taxonomies that come with the theme are set here). You shouldn't add the strings that end in "_rewrite_base" for translation in the WPML -> String Translation, as it will give error 404 on the translation pages.
For the strings that show on the property page (ex: "Garage size" or "Description"), you should check on WPML -> String Translation and translate those strings from there.
1. We recommended flushing the website's cache and then navigating to WP Admin -> Settings -> Permalinks to click the "Save" button, which flushes the permalinks.
2. We advised checking the documentation for using the Houzez theme with WPML, specifically for translating taxonomies:
- Creating multilingual real estate sites with Houzez theme and WPML
- Translating post categories and custom taxonomies
3. We instructed the client to add strings for translation from WPML -> String Translations -> Translate texts in admin screens, and to change the string language to "BG" as they are set to English by default.
4. We clarified that the string "features" from the domain "houzez_settings]property_feature_rewrite_base" should not be translated in WPML -> String Translation, as it is should be translated in WPML -> Settings -> Taxonomies Translation section.
5. For the author page translation, we explained that the bio/description found on the author's page in the backend is translatable using WPML -> String Translation -> More options. Also, the theme Houzez has a custom post type "Agents" and offers the possibility to translate it as any other default post type.
If this solution does not seem relevant to your situation, please open a new support ticket with us.
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.
This topic contains 34 replies, has 2 voices.
Last updated by 1 year, 11 months ago.
Assisted by: Marsel Nikolli.
 |
|
|
|
Also, I went to translate all strings from the Property page, example: hidden link Even though I've been able to find all strings and edit them in the Strings Translation (see example.png attached) they aren't being translated front-end. Ofc I tried with a cache-free tab, Incognito and VPN.    |
|
|
Same with "Garage", translated everywhere in Strings Translation but not translated in front end.  |
 |
Hi, Sorry for the late reply due to Christmas holidays. 1) I was able to check and the strings for related to the "Garage" and the the Property page could be found on the WPML -> String Translation-> Translate texts in admin screens » section. I already added those strings and they should be already translated I think. * I noticed that there might be some other similar strings that you need to translate so please check on the page I mentioned above by checking on that page for the string you want to translate (check screenshot attached: ex. You want to translate the string "Garage size", when you search on that page you'll see that on the right column it says "Not included in String Translation" and by adding it you'll be able to translate it). Please check our documentation for more detailed information:https://wpml.org/documentation/getting-started-guide/string-translation/finding-strings-that-dont-appear-on-the-string-translation-page/#translate-admin-and-settings-strings 2) Related to the taxonomy slug that it's not being translated, could you please create a new testing property with the same details in both languages and check if there is any difference? * Does the same issue happen with different feature term? Looking forward to your reply,  |
|
|
Hi, Thank you for your help, no worries for the delay I'm not expecting everybody to work everyday during holiday season. 🙂 OK great I understand I should also check in the "Translate texts in admin screens". I found 3 occurences of the string "Rooms" and it fixed the last word that was still being displayed in English. That seems all good here for now, thank you. The slug's issue is not related to any property in particular. It's more a "category" for example this page here lists all properties which have a backyard: Here: hidden link Anyway, I went along and created a new property to experiment with the "air conditioning" feature: hidden link When you click on the "Air conditioning" feature (see screenshot) it leads to: hidden link Which return a 404. If I change "features" by "harakteristika" however the page exists: hidden link But because this is the /en/ English version it should be "features" in the URL, not "harakteristika".  |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
I understand the situation, and I see that the agent fields are added as well on the author page in the backend (which I am guessing is already implemented to show up on the theme itself). Now that you checked the boxes in the WPML-> String Translation -> More options, you can find the strings for translation on the WPML -> String Translation under the domain "Author" (please check attached image). It would suggest checking what other plugin could work better with the theme you are using to to manage the website authors in order to get a better result. Maybe checking again with the theme dev team could be a start, in case the solution they already gave won't work out as you desire. Let me know if you need more assistance. Kind regards,  |
|
|
OK I found the strings. I have another issue now: hidden link This is the page for the Bulgarian version, yet the strings used are the English one. This is quite confusing, and when I want to access the English version of the same page, by clicking on the langage switcher, the page doesn't exist so I'm being redirected to the homepage instead of the translated version of the page.  |
|
|