Problem: The client has translated content into Welsh using the WPML plugin, but changes made in the backend do not appear on the frontend of the site. The client also encountered an issue where the expected popup for translation options did not appear, and received a warning about potential data loss when switching from the WPML Translation Editor to the native WordPress editor. Solution: We advised the client to disable the Advanced Translation Editor if they prefer using the native WordPress Editor for translations. This action is necessary to avoid conflicts and ensure that changes are correctly reflected on the site. For detailed steps on how to switch editors, we recommended visiting the following documentation: Using Different Translation Editors for Different Pages.
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: You are trying to translate a homepage from English to Spanish, but the system keeps setting Portuguese as the source/original language, even though you have already completed the English to Portuguese translation. Solution: First, we recommend duplicating the homepage and then attempting to translate the duplicated page into Spanish. This might resolve the issue of the incorrect source language setting. If duplicating the page does not solve the problem, we suggest providing us with a backup of your wp-content folder and your database. You can zip these files and share them via Google Drive. This will allow us to set up a local copy of your site and investigate the issue more thoroughly.
Please note that the solution provided might be outdated or not applicable to your specific case. We highly recommend checking the related 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 links with '/en' still appeared in the sitemap even though these pages were supposed to be deleted. Additionally, upon deleting the English version of a page, the language switcher button disappeared, which normally would redirect users to the homepage if a translation in the selected language was not available. Solution: 1. We confirmed that the translations existed and were not technically incorrect. To remove unwanted pages from the sitemap, the client should delete the posts in the secondary language from the WordPress admin, similar to how they would in the default language. 2. To address the missing language switcher button, the client needs to enable the option in WPML to redirect missing translations to the homepage. This setting is found under WPML > Languages. 3. For the issue with redirects, it was suggested to use more unique slugs for each language version of the pages to avoid conflicts, as using identical slugs in different languages can cause issues with WordPress and the server.
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: The client reported an issue with media translation paths when replacing an image uploaded in the same month as the original. This problem was specific to their setup and involved the Offload Media plugin. Solution: We suggested a workaround involving code changes in the Offload Media plugin. Specifically, the client needed to open
We also communicated with the plugin authors to seek a permanent fix. Meanwhile, the client can use this workaround as a temporary solution.
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 at WPML support forum.
Problem: You are unable to translate certain pages on your website using the Advanced Translation Editor or automatic translation. You receive an error message indicating that WPML tried to translate the page three times and failed. Solution: The issue might be caused by your hosting provider blocking the request through a firewall or another security layer, or the specific page may contain data or content that causes the translation job submission to fail. We recommend: 1. Updating the problematic widget on the original page by recreating it. 2. Alternatively, consider keeping and using the duplicated page instead of the original one.
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.
