Problem: You've noticed that since the last update, an image that's translated in the Media Translation, when used on a page and then translated in the CTE, isn't translated anymore. Instead, the original image is served on the translated page. Solution: We've resolved this issue in the latest version of WPML (4.9.0). Please also update to the new versions of Strings Translation (3.5.0) and Media Translation (3.1.0). If you don't see these new versions on your site, follow these steps: 1. In your site’s admin, go to Plugins → Add New Plugin and click the Commercial tab. 2. Click the Check for updates button. 3. Select WPML 4.9 from the list and click Install. Before updating our plugins, we strongly recommend making a full site backup (files and DB). Learn more about WPML 4.9.0 in our post: WPML 4.9.0 Changelog
If this solution does not apply to your case because it might be outdated or not relevant, we highly recommend checking related known issues at WPML Known Issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If issues persist, please open a new support ticket.
Problem: The client is experiencing an issue where the process of updating affected posts for changes in translatable fields is stuck on the 'custom_title' custom field after updating WPML and String Translations plugins. The process is halted at 50 entries and does not progress despite retries. Solution: 1. Ensure that all WPML plugins are updated to their latest versions. 2. Backup the entire site. 3. Run all troubleshooting options available under WPML > Support > Troubleshooting, except for those that involve resetting. 4. If the issue persists, consider truncating the 'icl_background_tasks' table and re-uploading the initial database before updates. 5. Check server and PHP configurations, as discrepancies in these settings across different environments might contribute to the issue. 6. If none of the above steps resolve the issue, we recommend opening a new support ticket. Additionally, it's advisable to 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.
If these steps do not resolve your issue, please do not hesitate to contact us for further assistance by opening a new support ticket at WPML support forum.
Problem: You are experiencing inefficiencies in uploading images with localized filenames for SEO purposes using WPML Media Translation. You've noticed there is no automatic process for translating filenames, which makes the process time-consuming. Solution: We have considered the possibility of implementing automatic filename translation. However, after internal discussions, we decided not to pursue this feature at the moment. The main reasons are the lack of sufficient demand from our users and the potential increase in database usage due to file duplication. WPML is designed to focus on translating user-generated content like alt texts and captions while using the same media file across different translations.
If this solution does not resolve your issue or seems outdated, we recommend checking the related known issues and verifying that you have the latest versions of themes and plugins installed. If the problem persists, please open a new support ticket.
Problem: You have over 25,000 strings in WPML that are 'not used or linked to the wrong translation data', and you're unable to remove them efficiently through the interface due to the large volume and server limitations. Solution: If you're experiencing this issue, we recommend the following steps: 1. Ensure you take a backup of your site. 2. Download and activate the provided plugin from https://we.tl/t-BpP6RmeVea. 3. Append
?delete_strings=1
to your site's dashboard URL and reload the page. This will delete strings in batches of 5000. 4. Refresh the page multiple times until all strings are deleted, as indicated by a confirmation message. 5. Visit the WPML troubleshooting page and verify that there are no strings needing deletion. 6. Run the 'Cleanup and Optimize String Tables' step from the troubleshooting page. 7. Deactivate and remove the plugin after completion.
This solution is a temporary workaround. We are aware of the need for a more permanent fix and are working towards it. If this solution does not apply to your case, or if it becomes outdated, please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and ensure you have installed the latest versions of themes and plugins. If further assistance is needed, we highly recommend opening a new support ticket at WPML support forum.
Problem: The client was experiencing an issue where French images were not displaying on the French page despite using WPML's Media Translation. The issue occurred after updating content through the Classic Translation Editor (CTE) and also after updating WPML on a local environment. The CTE was offering English media for the French translation after these updates. Solution: The issue was resolved by the client by clearing caches, deactivating, and sometimes re-saving the original content, then reactivating the caching. It was noted that issues might be related to the interaction between WPML and the W3 Total Cache plugin, even with the Pro extension designed to handle WPML specific requirements.
If this solution does not resolve your issue, or if it 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 problems persist, please open a new support ticket.
Problem: You are receiving an unsynced taxonomy warning despite the taxonomies being synced. Solution: 1. Object Cache: If your site uses object caching, the warning might be stored there. We recommend clearing the object cache to resolve this issue. 2. Cache Folder: Ensure that the
/wp-content/cache/
folder is writable. This issue can arise if the folder becomes non-writable, especially after site migrations, which prevents proper cache purging. 3. Database Cleanup: Consider manually removing the
wpml_notices
and
icl_admin_messages
entries from your database. 4. Large Taxonomy Sets: If your taxonomy has many terms, it might not be processed completely. We recommend checking the documentation on Translating many taxonomy terms. Please ensure to have a full website backup before making any changes based on our recommendations.
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. If you still need assistance, please open a new support ticket at WPML support forum.
Problem: You are trying to translate a post to a different language using an XLIFF file with the Classic Translation Editor (CTE), but the translated page is not visible on the frontend unless its URL is different from the original. This issue was previously resolved for the Advanced Translation Editor (ATE), but not for the CTE. Solution: The issue is related to caching. After translating a page using the CTE, you need to clear the caches of W3TC (W3 Total Cache) to make the translated page available. If you do not clear the cache, you will be redirected to the original page when attempting to access the translated page.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 WPML support forum.
