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.
Problem: The client is working on a site under development and needs guidance on which editor to use for editing a translation after importing it from XLIFF. The client uploaded an XLIFF file for a translation from English to Italian. After uploading, the translation appears on the frontend, but some segments still need translation. However, in the Advanced Translation Editor (ATE), all segments appear empty. Solution: We recommend using the Classic Translation Editor (CTE) for editing translations imported from XLIFF files. Unlike ATE, CTE supports the display of HTML markup and can handle XLIFF imports effectively. ATE, designed to run on an external server with a different code base, does not support these features and only displays pure text. If you are using XLIFF import/export, CTE is the appropriate tool as it is compatible with XLIFF files and supports markup language.
Please note that while new features for CTE are not anticipated, it will remain available in future versions of WPML as many clients rely on it. There are currently no known issues with using XLIFF files in CTE, which you can verify at known issues.
If this solution does not resolve your issue or seems outdated, 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client is unable to upload SVG files through WPML Media Translation after updating WPML plugins. They encounter a default image or a 'Security check failed' message depending on the SVG plugin used. This issue persists across multiple environments. Solution: We recommend verifying the compatibility of the SVG plugin with WPML. WordPress does not natively support SVG, and third-party plugins like 'Safe SVG' might not be compatible with WPML. Check if the plugin has been updated recently and might require a compatibility update with WPML. Encourage the plugin author to join WPML's Go Global program to ensure compatibility. For more details, visit WPML's Go Global program.
However, if the problem is outdated or if you have further questions, feel free to 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, please visit our support forum at WPML support forum.
Problem: The client is uncertain whether the WPML Translation Management plugin is still necessary for working with XLIFF files, given that it has been labeled a legacy add-on since WPML version 4.5. Solution: If you're experiencing similar confusion about the necessity of the WPML Translation Management plugin for handling XLIFF files, we recommend understanding that in the current version of WPML, the "Translation Management" functionality is integrated within the WPML Multilingual CMS. Therefore, the separate add-on is no longer required for exporting and importing XLIFF files.
This solution might be irrelevant if it's 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 this does not resolve your issue, please open a new support ticket at WPML support forum.
Problem: You are trying to translate content using WPML, but after a few validations, you cannot validate any more segments. Pressing Ctrl+Enter or the save button does not work, and you are not moved to the next segment. Reloading the page temporarily resolves the issue, but it recurs shortly after. Solution: We recently released an update for the Advanced Translation Editor, which should resolve this issue. Please edit the original content, save the page, and then try to apply the translation again. If the problem persists, 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 this solution does not resolve your issue or seems irrelevant, please open a new support ticket at WPML support forum for further assistance.
Problème : Vous tentez de traduire des custom fields ajoutés sur des catégories produits WooCommerce via un fichier JSON géré par ACF, mais vous rencontrez des difficultés pour les rendre accessibles dans WPML > Settings > Custom Fields Translation, même avec l'option 'show System fields' cochée. Les champs sont visibles dans Custom Terms, mais pas dans l'endroit attendu. Solution : 1. Assurez-vous que les custom fields pour les catégories WooCommerce, qui sont considérées comme une taxonomie, soient cherchés dans 'Custom Term Meta Translation' plutôt que dans 'Custom Fields Translation'. 2. Vérifiez les paramètres de traduction dans WPML et ACF. Pour les champs textuels et les images, ils doivent être déclarés avec l'option 'Translate' pour être traduisibles via l'éditeur de traduction. Pour les images, vous pouvez également utiliser l'option 'Copy' pour que l'ID de l'image d'origine soit copié comme valeur de traduction, ce qui permettra d'appeler l'image traduite via Media Translation. 3. Alignez vos paramètres de mode de traduction dans les réglages WPML et ACF pour obtenir le comportement désiré.
Si cette solution ne résout pas votre problème ou semble dépassée, nous vous recommandons de vérifier les problèmes connus, de confirmer que vous avez installé les dernières versions de vos thèmes et plugins, et si nécessaire, d'ouvrir un nouveau ticket de support sur notre forum de support.
Problem: If you're experiencing issues where the original image isn't displayed on the frontend for product translations, and changes are not reflecting immediately, it might be due to insufficient memory limit settings. Solution: We recommend increasing the WordPress memory limit. You can do this by editing the
wp-config.php
file located in the root folder of your WordPress installation. Find the line:
define('WP_MEMORY_LIMIT', '256M');
and change it to:
define('WP_MEMORY_LIMIT', '512M');
This adjustment should help in resolving the issue with images not showing up directly on the frontend.
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 problem persists, please open a new support ticket at WPML support forum for further assistance.
