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.
Problem: You are working on a site under development and have encountered an issue where you no longer have access to the Advanced Translation Editor (ATE) via the WordPress all pages section. Additionally, you need guidance on correcting a translation mistake on a page. Solution: First, ensure that the Advanced Translation Editor is enabled by navigating to WPML -> Settings -> Translation Editor. Then, open a page in the default language editor and verify that "WPML editors" is enabled in the language metabox, typically found on the right side of the screen. If you still cannot access the Advanced Translation Editor after these steps, please go to WPML -> Support -> Advanced Translation Editor -> Error Logs and send us a screenshot of any relevant logs.
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. Additionally, please feel free to open a new support ticket for further assistance at WPML support forum.
Problem: You are seeing obsolete URLs in the WPML translation editor, which include URLs that should not be up for translation and some that contain two slugs or non-existent URLs. Solution: The issue arises because these URLs are still associated with specific page IDs in your database, even if they are no longer active or relevant. This can happen if data from previously used plugins (like Yoast) remains in your database even after the plugin is removed. To resolve this, we recommend checking your database for any residual data linked to these page IDs and removing them if they are no longer needed. This cleanup will help ensure that only relevant and current URLs appear in the WPML editor.
If this solution does not apply to your case, or if it seems outdated, please check the related known issues and confirm that you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket at WPML support forum for further assistance.
Problem: When navigating into the French folder in the WordPress Dashboard under Pages->All Pages, both WordPress and Yoast SEO switch to French, even though the default language is set to English. Solution: If you're experiencing this issue, we recommend you navigate to your WordPress Dashboard > Users > Profile. Here, you will find an option labeled Set admin language as editing language. Uncheck this option to prevent WordPress and Yoast SEO from switching to French when accessing the French folder.
Please note that this solution might be irrelevant if it's 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 at WPML support forum for further assistance.
Problem: The client is unable to save new settings permanently in WPML. After refreshing the browser page, old settings reappear instead of the newly saved settings. Solution: If you're experiencing this issue, we recommend clearing the caches on your site and server first. If the problem persists, try disabling all plugins except for WPML, String Translation, and Elementor to check for a plugin conflict. Reactivate the plugins one by one, saving the WPML settings after each to identify the problematic plugin.
For issues related to media settings not saving, understand that options like Duplicate existing media for translated content and Duplicate the featured images for translated content are not permanent settings but troubleshooting tools. Changes made under "How to handle media for new content:" in the Media Translation settings will be saved permanently.
To translate image meta information, enable "Translate media library texts with posts" under WPML > Settings → Media Translation. Ensure the "Duplicate" option in Media Translation settings is enabled for the image data to be available in the Advanced Translation Editor.
If these steps do not resolve your issue, or if the solution 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: You are unsure about the functionality of the Duplicate options in WPML's Media Translation. Solution: The 'Duplicate' option in WPML means that WPML will create a separate database entry for each image in each language. This results in one entry inside the media library for the media in each language, while using the same source file across all languages. For more detailed information on how to manage media translations, we recommend checking the WPML Media Translation documentation.
If this solution does not apply to your case, or if it seems outdated, please open 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, you can always contact us through the WPML support forum.
Problem: You are experiencing an issue where the Advanced Translation Editor (ATE) displays 9 images for translation, but only 5 images are visible on the frontend page. Solution: This discrepancy may occur if media was previously part of the content and then removed. To address this, follow these steps: 1. Navigate to your media library, switch to list view, and detach the media files from the content. This action will not remove the images from the content. 2. Go to WPML > Settings > Media Translation and uncheck the option "Translate media library texts with posts". This should resolve the issue temporarily. 3. For translating meta information, you can use WPML > Media Translation or directly inside the media library by changing the admin language in the top admin bar.
If this solution does not fully resolve your issue or seems outdated, we 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.
