Problem: The client was trying to translate the homepage with slider blocks but encountered issues where the translation page was not 100% complete, and there were errors in the console. The translation inconsistencies included links and slider images not being translated correctly, and sometimes the translations were not saved. Solution: 1. We confirmed that external links need to be manually translated as detailed in the documentation: https://wpml.org/faq/how-to-translate-links/ 2. We identified an incompatibility with the slider plugin on the English version of the page. To resolve this, we manually edited the English language page to fix the broken slider. After these adjustments, the slider functioned correctly.
If this solution does not resolve your issue, or if it 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: The client reported that texts in the fields for the English language on an Advanced Custom Fields options page changed to Russian unexpectedly. Other languages displayed correctly.
Solution: We attempted to reproduce the issue by: 1. Opening the options page in the default English language. 2. Changing some section texts back to English and saving. 3. Switching to Russian to check if the changes were overwritten and then saving. 4. Switching back to English to confirm if the changes persisted.
Since the issue could not be reproduced, we suggested that the client monitor the site closely and isolate the issue on a staging site if it occurs again. It's important to note any special activities or workflows that might influence the language settings.
If this solution does not resolve your issue, or if it 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 the problem persists, please open a new support ticket at WPML support forum.
Problem: The client needed to translate PDF vouchers but encountered an issue where the product attribute was showing in the original language (LT) instead of the translated language (EN) when using the shortcode
{variationname}
provided by the voucher plugin. Solution: We recommended that the client should create a copy of the original template post and set it as English. If the product attribute still appears in the wrong language, we suggest checking the translation settings for the product attributes within WPML and ensuring that the translations are correctly configured. Additionally, it may be necessary to consult with the voucher plugin authors to ensure that their shortcode is compatible with WPML and is able to display translated attributes.
Please note that the solution provided might be outdated or not applicable to your case. If the issue persists, 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 you still need assistance, please do not hesitate to open a new support ticket with us.
Problem: The client was experiencing issues with anchor IDs not being available for translation.
Solution: We added a custom XML configuration to make the anchor IDs translatable. The client should now be able to translate them. Here is the XML code we used:
If you're experiencing a similar issue, we recommend trying the provided XML configuration. However, please note that this solution might be outdated or not applicable to your case. If it doesn't resolve your issue, we encourage you to check the related known issues, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If you still need assistance, please don't hesitate to open a new support ticket with us.
Problem: The client was experiencing issues with Media Translation not working in Gutenberg, specifically with anchors not showing up for translation.
Solution: We recommended that the client incorporate a custom XML configuration into WPML. Here is the step-by-step process: 1. Navigate to WPML > Settings > Custom XML Configuration tab. 2. Insert the following custom XML configuration:
3. Make slight adjustments to the primary language page and re-translate it. 4. In the advanced Translation Editor, attempt to locate the image name.
If the solution provided does not resolve the issue or seems irrelevant due to being outdated or not applicable to your case, we highly recommend checking 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 problem persists, please open a new support ticket with us.
Problem: The client is experiencing issues with the Advanced Translation Editor (ATE) separating sentences incorrectly, particularly when a dot follows a year mark, making it difficult to translate content as a coherent sentence. Solution: We recommend joining the segments in ATE to improve the translation process. This can be done by following the steps outlined in our documentation on joining sentences. Please note that after joining segments, they will need to be translated again. This is because ATE saves translations per segment in the Translation Memory, and joining segments helps the automatic translation to work better, especially if a sentence is split into too many segments, which can affect grammar and meaning.
If this solution does not apply to your case, or if it seems outdated, we encourage you to open a new support ticket. We also 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. For further assistance, please visit our support forum.
