Problem: If you're experiencing a critical error when accessing the Media Translation feature in the WPML plugin, and the error message indicates a type mismatch in the constructor arguments for WPML_Media_Translations_UI, this might be due to a version mismatch between Media Translation and String Translation. Solution: We recommend updating all outdated plugins and themes. If the issue persists, follow these steps: 1. Ensure that your site is registered with a valid key. 2. Deactivate all plugins and switch to a default WordPress theme to check if the issue is resolved. 3. Reactivate your theme and plugins one by one to identify the problematic component. 4. Once identified, contact the support service of the theme or plugin causing the issue.
If this solution does not resolve your issue or seems outdated, please 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 necessary, do not hesitate to open a new support ticket.
Problem: When you click 'Edit Translation' on the admin bar of a translated page, it transfers you to the Advanced Translation Editor (ATE), shows that the translation is 100% complete, then redirects back to the translated page with the message 'Please wait, applying translation...'. However, the translated text or changes from the source page are not applied to the translated page. A fatal error indicating an improperly formed xliff file was found in the debug log. Solution: Our ATE team solved the issue and this is fixed on WPML Advanced Translation Editor's side.
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 issues persist, please open a new support ticket at WPML support forum.
Problem: The client wants WPML to automatically scan internal links from default/custom Gutenberg blocks and ACF Link fields to ensure that users are directed to the correct language version of a page. They encountered issues where changes on the source page were not applied to the translated page. Solution: For ACF Link fields, the translation preference should be set to 'Translate' to allow for automatic scanning of links. For custom Gutenberg blocks, if they are rendered via React using a JSON data prop, the internal links might not automatically update to point to translated pages. In such cases, disabling WPML Translation for the specific page and translating it manually with the default WordPress editor is recommended as a workaround. More details can be found here: Using different translation editors for different pages. Additionally, a separate ticket was created to address the issue of changes not being applied to the translated page, which can be followed here: WPML support forum topic.
If this solution does not resolve your issue or seems outdated, we recommend opening a new support ticket. We also advise 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.
Problem: The client was experiencing an issue where the Advanced Editor jobs synchronization failed when using PHP 8.4, redirecting them to the Translations queue instead of the translation tool. Solution: 1. We recommended downgrading the PHP version to 8.2 or 8.1 and ensuring that WPML is updated to version 4.8.1. 2. We advised activating the WordPress debug mode and checking the debug.log for errors when PHP 8.4 is active. The instructions for activating debug mode can be found here: https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/ 3. We suggested deactivating all plugins, including WPML ones, activating a default WordPress theme like Twenty Twenty, and then reactivating the WPML plugins. If the issue disappeared, the client was to reactivate the theme and other plugins one by one to identify the culprit. 4. Since PHP 8.4 is not fully supported by some WordPress functionalities, we recommended contacting the hosting provider to check server-side logs for any errors.
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 trying to translate a US English web page to British English and duplicate all the graphics and layout from the source page, but the header image and other media items are missing in the US English version's media library. Solution: If you're experiencing this issue, we recommend navigating to WPML > Settings > Media Translation. Ensure the following options are checked:
Translate existing media in all languages
Duplicate existing media for translated content
Duplicate the featured images for translated content
After confirming these settings, back up your site and click on the "start" button. This action will resync and ensure that all translated media is available.
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 at WPML support forum for further assistance.
Problem: You are trying to translate text using the WPML tool in WordPress, but some text is not being caught by the WPML translation tool. When you manually translate text directly in the WP Gutenberg editor and later update the content using the WPML translation editor, the manually translated text reverts back to the original language. Solution: You cannot use the Advanced Translation Editor (ATE) and manually edit content in Gutenberg simultaneously as this causes translation issues. You need to choose either to continue using ATE exclusively or to manually translate all content. If certain texts are not detected by ATE, it might be due to a compatibility issue with the plugin generating the Gutenberg block. If the plugin is tested and supported by WPML, we can help investigate the issue. If not, you should contact the plugin developer to make their plugin compatible with WPML. You can find guidance on making custom Gutenberg blocks translatable here: Make Custom Gutenberg Blocks Translatable. Additionally, if you prefer to use manual translation for specific pages, follow the steps outlined here: 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 at WPML Support Forum.
