Problem: The client updated their contact page in English and then updated the French translation through the editor. However, the changes did not appear on the French version of the contact page. The French contact page showed an old address and was missing a second phone number, despite updates made in the editor. Solution: We recommended the following steps: 1. Edit the page in the original language. 2. Make some changes in the content. 3. Save the changes. 4. Update the translation. 5. If the issue persists, manually edit the translated page, add the changes to the contact information, and save the changes. 6. Double-check if the content appears correctly translated. It turned out that the issue was due to a missing translation for the new contact information. Since the editor was loading the full block in HTML, it was necessary to manually change the translation. We completed the translation for the client, cleared the cache, and confirmed that it was working as expected.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client was experiencing issues with their WordPress site after updating the Elementor and Elementor Pro plugins. Specifically, the fonts on the French version of the website changed, and agents were not being assigned to translated properties, causing them not to appear on the 'À propos' page.
Solution: For the font issue, it was discovered that the problem was due to CORS policy errors blocking the custom fonts from being loaded. The solution involved resetting the theme, which resolved most of the font issues. However, for complete resolution, adjustments related to CORS policy might be needed, which involves server settings and possibly contacting the hosting provider.
For the agent assignment issue, the WPML support team adjusted the custom field settings to 'copy' so that the agent assigned in the original property would automatically be copied to the translated property. Additionally, specific code modifications were suggested to ensure that the agent ID is correctly recognized across different languages in the Houzez theme. These changes involved adding filters to apply the correct agent ID based on WPML's language settings.
If these solutions do not resolve your issues or 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. If further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client was unable to find how to translate the word 'City' into French 'Ville' using WPML. Solution: We accessed the WPML String Translation section and found that the word 'City' was already set to 'city' in French. We updated this to 'Ville' as required. If you're experiencing a similar issue, we recommend checking the WPML String Translation tool and updating the translation as needed.
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 persists, please open a new support ticket.
Problem: The client reported that the English version of their website was displaying mixed content in English and French, including forms and property details. This issue seemed related to the translation settings in the theme's backend, where languages were mixed without any recent changes made by the client.
Solution: We advised the client to ensure they are using the latest versions of the WPML plugins by checking for updates in the Plugins > Add New > Commercial section. We also suggested re-adding strings in the default language and re-translating them to check if the issue persists. Additionally, we recommended not translating labels from the theme options but using the WPML String Translation instead. If the problem continues, we suggested creating a staging site for further debugging to avoid issues on the live site.
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 persists, please open a new support ticket for personalized assistance.
Problem: The client reported multiple issues: not receiving notifications, mixed language content in posts, missing translations on a specific page, and incorrect translation of an icon label. Solution: 1. We investigated the notification issue and advised the client to check and adjust email notification settings in their WPML account. 2. For the mixed language content, we corrected an XML code that was affecting content detection by WPML in Elementor, allowing proper reloading and translation of titles. 3. Missing translations were addressed using the WPML String Translation tool, with specific guidance provided for strings affected by HTML styling. 4. The incorrect icon label was also corrected via String Translation. 5. We recommended not using page editors like Elementor for editing translations as it could lead to errors or loss of data.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client was facing two issues: firstly, the Mailchimp form workaround was not effective, and secondly, there was confusion regarding the translation of footer items due to overlapping taxonomy strings. Solution: For the Mailchimp form, we advised the client to navigate to WPML->Theme and Plugins Localization, select the Mailchimp for WordPress plugin, and scan it for strings. Although WPML found 338 new strings, the placeholder was not included. We recommended trying another workaround, which can be found here: https://wpml.org/forums/topic/how-can-i-translate-the-mailchimp-form/#post-14107851. For the footer items, the issue was identified as overlapping taxonomy strings where 'agent_city' and 'city' were both translated to 'ville'. We reverted the translations to 'city' and 'agent_city' as a test and are currently conducting further testing.
Please note that the solution provided 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 persists, please open a new support ticket at WPML support forum.
Problem: The client needed to translate the submit button on their French version of the website but was seeing 'Submit' instead of 'Soumettre'. The issue persisted even after attempting initial solutions. Solution: We recommended the client to try the following steps: 1. Go to the site's backend, switch to French from the top black bar, navigate to Pages, find the relevant page, hover over it, and select 'Edit with Elementor'. Then, edit the form to change the button label and save the page. 2. If the button still doesn't translate, use WPML's String Translation to locate and translate the string. This might involve enabling the 'Look for strings while pages are rendered' option under WPML > String Translation, visiting the page where the string is displayed, and then searching for the string again in WPML. 3. Alternatively, check if the strings are included as admin text strings, which can be translated following the process described here. Related documentation can be found here.
Please note that the solution might be irrelevant due to being outdated or not applicable to your specific case. If these steps do not resolve your issue, 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 needed, please open a new support ticket here.
Problem: The client is experiencing an issue where the favicon icon does not appear on Google search results for the French version of their website. Solution: We have verified that the favicon appears correctly on the French version of the website. It is possible that Google may need more time to update its search results. We recommend waiting a few weeks to see if the issue resolves itself.
If the problem persists or if this solution becomes irrelevant due to updates or it does not apply 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. Additionally, feel free to open a new support ticket with us for further assistance at WPML Support Forum.
Problem: The client was unable to validate a newly purchased domain for the French version of their website during the WPML setup. Additionally, they encountered issues with missing translations and incorrect content display on specific pages of the French site. Solution: We recommended switching to 'Different Languages in Directories' and finalizing the configuration setup. After this, the client should switch to 'different domains per languages', add their URL, uncheck the 'validate on save' option, and save the settings. For the content issues, we accessed the site and manually updated the affected pages by switching to the secondary language in the WP editor and clicking update. We also synchronized the taxonomies from within WPML to fix the footer display issues. For the missing translations, we advised verifying that all strings are fully translated in WPML->String Translation and checking the source of these strings. For further details on manual translation and theme compatibility, please review the following documentation:
If the solution provided here does not resolve your issue or 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 further assistance is needed, please open a new support ticket at https://wpml.org/forums/forum/english-support/.
