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.
Problem: The client is experiencing issues with Offload Media, specifically duplicated entries in the database, and is unsure about the functionality of certain WPML Media Translation settings. They observed that when translating posts through the editor with specific settings untoggled, the featured images are not copied, although content images are. Solution: We explained that the behavior of media in WPML is as expected. If the 'Duplicate existing media for translated content', 'Duplicate the featured images for translated content', 'Duplicate media attachments for translations', and 'Duplicate featured images for translations' settings are not enabled, the system does not duplicate or translate these elements. Specifically, for featured images to be translated or duplicated, the relevant checkbox must be checked. Then, the images should be managed via Translation Management to ensure they are correctly assigned per language. When translating a post that includes an image within its content and the media functionality is disabled, the original image from the default language is displayed unless adjusted by other settings or filters, such as those used by some page builders.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 problems persist, please open a new support ticket.
Problem: The client has migrated their content from the Classic Translation Editor to the Advanced Translation Editor (ATE) in a test environment and is considering cleaning up the database after the migration, despite the content being mostly individually edited. Solution: We recommend continuing to use one editor, the Advanced Translation Editor, for all site content to maintain consistency and ease of use for translators. After switching from the Classic Translation Editor to the Advanced Translation Editor, existing translations will still be visible on the frontend. However, these translations might be completely or partially missing when opening the post in the Advanced Translation Editor. For more details, you can visit Switching from Classic to Advanced Translation Editor. Additionally, there is no need for a database cleanup after moving to the new editor, even if the content was initially translated using the Classic Editor.
If this solution does not resolve your issue or seems outdated, 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 if needed.
Problem: The client is developing a site and using WPML to streamline the translation workflow. They have a custom field to set a menu on a specific post type and want the same menu on translated pages without needing to translate the menu name or set it manually each time. They are experiencing issues with unnecessary translation requests for some values. Solution: We explained that there isn't a specific option to control this behavior directly when it's set to 2, as the ACF translation is activated regardless of the input provided. We suggested using the "Different fields across languages" option, which allows translating the input method directly as a string. For more details, see the documentation on translating ACF field labels with WPML.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also highly suggest 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.
