Problem: The client is experiencing issues with visitors being directed to sub-directory URLs instead of the correct domain URLs after changing the WPML-Language setting for different domains. Additionally, there are problems with a distorted home page and missing background images when switching to French. Solution: After migrating from staging to production please run the WPML troubleshooting options available at WPML > Support > Troubleshooting (Cleanup) > Clear the cache in WPML. This action can help resolve issues inside the Advanced Translation Editor.
If this solution does not resolve issues or seems irrelevant due to being 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. Should you need further assistance, please do not hesitate to open a new support ticket at our support forum.
Problem: If you're experiencing multiple sentences appearing in the same segment (row) in the Advanced Translation Editor (ATE). Solution: We recommend you adjust your ATE settings. In the Advanced Translation Editor, click on the settings icon located in the right upper corner. Here, disable the option
I prefer bigger segments
. Please note, these changes will only affect new translation jobs. To apply this setting, edit your original content, save it, and then reopen the translation editor. This option is enabled by default in the new Gen3 UI of the Advanced Translation Editor.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: You are experiencing an error after moving your site from staging to production, with a message indicating that WPML detected a new address for the site, although the address has not changed. Solution: We recommend ensuring that each site version (staging and production) has a unique site key. During the migration process, you should select the 'copy' option on the migration banner. However, it is crucial to generate a new site key for the production site.
If this solution does not resolve your issue or seems irrelevant due to being 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. Additionally, please feel free to open a new support ticket with us for further assistance at WPML support forum.
Problem: The client needed to remove the year 2002 from their website, where it incorrectly displayed as 2002-2024 instead of just 2024. Solution: We located the string using the 'Look for strings while pages are rendered' option in WPML > String Translation. The string was found under the domain 'Widgets' with the name 'widget body'. We made the necessary adjustment to display only the year 2024. If you're experiencing this issue, we recommend trying these steps to adjust the string as needed.
Please note that this solution might be outdated or not applicable 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 issue persists, please open a new support ticket.
Problem: When using WPML with Elementor, after editing a translation in the Advanced Translation Editor (ATE) and refreshing the page in Safari, the changes are not consistently reflected. This issue occurs especially after clearing the Safari cache and refreshing the page multiple times. Solution: Disabling "MemCached" on the server helps If these steps do not resolve the issue or if the solution provided here is outdated or not applicable 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 here.
Problem: The client was trying to update the production license key after moving from staging to production but encountered an error stating that the site is still registered as a development site on WPML.org. Solution: If you're experiencing this issue, we recommend following these steps: 1. Unregister your site from being recognized as a development site by following the instructions here: How to remove the 'This site is registered on WPML.org as a development site' notice. 2. After unregistering, go to your WPML account and delete the old key as shown in your account screenshot. 3. Re-register your license for the production environment.
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 problem persists, please open a new support ticket.
Problem: The client is using WPML with Elementor on a site under development and is concerned about whether to prevent Elementor from autosaving translated posts. They also reported issues with changes not reflecting in Safari after clearing the cache and refreshing the page. Solution: We confirmed that there should not be any issues with the autosaving feature of Elementor when used with WPML, as WordPress's autosave feature has not shown conflicts with WPML either. If you're experiencing specific issues with WPML, we recommend opening a new support ticket for each unique problem for proper investigation. Additionally, if browser compatibility concerns arise, testing the procedure on a different browser might help identify if the issue is browser-specific. For ongoing or unresolved issues, we encourage opening a new ticket to ensure all problems are addressed. If the issue is related to WPML or possibly another plugin or theme, our developers will investigate and may find a workaround or suggest joining our 'Go Global' program (https://wpml.org/documentation/theme-compatibility/go-global-program/) to ensure compatibility.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. We highly recommend opening a new support ticket at https://wpml.org/forums/ for further assistance.
Problem: The client is experiencing an issue where all SEO score bullets are grey on the translated French pages in WordPress, indicating a potential problem with the SEO implementation on these pages. Solution: We recommend the following steps to address the issue: 1. Edit a page and verify if the SEO options are correctly applied. 2. Ensure you are following the steps outlined in the WPML documentation for using WordPress SEO with WPML, which can be found here: https://wpml.org/documentation/plugins-compatibility/using-wordpress-seo-with-wpml/. 3. Try disabling all non-WPML plugins and switch to a default theme to see if the issue persists. Remember to back up your site (both files and database) before making any changes.
If these steps do not resolve the issue, or if the solution seems outdated or not applicable 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 continues, please open a new support ticket at WPML support forum for further assistance.
