Problem: You are trying to configure the URL structure for translated pages on your site using WPML, aiming to retain the default language slug after the domain and language code. However, the translated page's slug changes to the translated language, resulting in URLs not maintaining the default language slug. Solution: Although WPML does not have a built-in option to keep the default language slug in translated URLs, you can achieve a similar result by following these steps: 1. Navigate to WPML → Settings → Page URL and set it to "Translate". 2. Manually set the slug in the translation editor to match the original. 3. Enable the option "Copy from original language if translation language uses encoded URLs". 4. Visit
If this solution does not apply to your case, 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. Should you need further assistance, please open a new support ticket at WPML support forum.
Problem: You are unable to save translations on your website because the original content includes formatting markups. Solution: First, ensure you have a full backup of your website. Then, follow these steps: For translating the menu: 1. Navigate to Appearance > Menus; 2. Switch to Azerbaijani in the top bar; 3. Delete the translation of the menu; 4. Switch back to English and select the main menu; 5. Click on the "+" sign to add a translation for Azerbaijani.
For translating search features and other fields: 1. Go to WPML > Theme and plugin localization; 2. Select and scan your theme and other plugins related to those features; 3. Navigate to WPML > String Translation, search for the texts, and add their translations.
If these steps do not resolve your issue, or if the solution seems outdated or not applicable to your case, we recommend opening a new support ticket. Additionally, 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. For further assistance, please visit our support forum at https://wpml.org/forums/forum/english-support/.
Problem: The client is unable to save translations in WPML because the original content includes formatting markups, and the client is unable to apply similar markups in the translated text. Solution: 1. Ensure that the original text and the translated text have matching markers. If the original text includes specific markers, these need to be replicated in the translation. For guidance on setting markers, refer to WPML documentation on safe HTML editing. 2. Check if the URL field in the translation editor is locked or empty. Unlock the field and ensure it is not left empty as this can prevent saving. 3. If issues persist, providing WordPress admin credentials to the WPML support team can help in directly investigating and resolving the issue.
Please note that this solution might be outdated or not applicable to your specific case. We highly recommend checking related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the problem persists, please open a new support ticket.
Problem: If you're experiencing issues with translating featured fields headings like 'handover', 'property type', 'price', etc., or if the phone number in the footer is not displaying correctly, starting from right to left and altering the structure, we can help. Solution: For translating the featured fields headings, we recommend you navigate to WPML > String Translation. Here, search for the strings you need to translate, such as 'Price', and ensure you mark the checkbox for 'Exact match'. Once found, add your translations accordingly. We have successfully applied this for 'Price', and it should work similarly for other fields. Regarding the issue with the phone number formatting in the footer, this typically occurs due to right-to-left (RTL) text settings that might be affecting your theme or custom CSS. We suggest checking your theme's RTL settings or reviewing any custom CSS that might influence text direction. If these suggestions do not resolve your issue, it might be due to reasons that are either outdated or specific to your 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 problem persists, please open a new support ticket at WPML support forum for further assistance.
Problem: The client reported that property listings were not appearing on the homepage or any other pages after translation. The featured properties were supposed to display in the website's header as a hero slider, but they were not showing up in the Arabic version.
Solution: 1) We identified that the URLs for the properties were translated before the URL settings were encoded. We edited the URL of the Arabic page to correct this.
2) We asked the client how they were setting the slider in the default language homepage and selecting what to show in the slider, to understand the setup better.
3) For taxonomy images, we set the custom field
fave_taxonomy_img
to copy from WPML > Settings > Custom Term Meta Translation. The client needed to resave the default language taxonomy for it to be saved/synced for translation. We performed a bulk update for the City images in Arabic to ensure they were synced.
If this solution does not resolve your issue, or if it seems outdated or not applicable to your case, we recommend opening a new support ticket. We also 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. For further assistance, please visit our support forum at WPML Support Forum.
Problem: The client needed confirmation on the calculation of 1.5 million credits for translating their website into multiple languages and requested an estimate of potential monthly costs under a Pay-as-You-Go plan. Solution: We confirmed that the client's calculation of 1.5 million credits costing approximately €512 was correct. We also clarified that under the Pay-as-You-Go plan, the monthly costs would depend on the actual words/credits used; there is no fixed monthly fee, and if no credits are used, no charges apply.
For further assistance with specific WPML functionalities or issues, we recommend visiting our support forum at https://wpml.org/forums/. Additionally, it's advisable to check for any related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and ensure that the latest versions of themes and plugins are installed. If the provided solution does not resolve your issue or seems outdated, please open a new support ticket.
Problem: The client is trying to translate their website into Arabic and other languages using WPML but is facing issues with poor translation quality and difficulties in translating the Header, Menu, Footer, and property listings. Solution: 1. For improving translation quality, we recommend adjusting the translation engines from WPML > Settings. 2. To translate the Header, Menu, and Footer, which are built using Elementor, follow the guide on translating Elementor Header template. 3. For translating menus, refer to translating menus documentation. 4. Check the theme-specific issues and workarounds for the Houzes theme at Translate Theme with WPML and WPML theme compatibility for Houzez.
If these solutions do not resolve your issues or if they seem 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. Should you need further assistance, please open a new support ticket at WPML support forum.
