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.
