Problem: The client is unable to delete a category translated by WPML. The deletion action from the WordPress categories screen has no effect, with no visible error but the action is blocked.
Solution: 1. Manage category deletion via WPML’s Taxonomy Translation interface. 2. Clear all translations of the category by emptying the translation fields in each language and saving. 3. Attempt deletion again via Posts → Categories after clearing translations. 4. If the issue persists, activate WordPress debug mode as described in Debugging in WordPress and check for JS/PHP errors in the browser console or error logs during deletion. 5. If no errors are found, test for plugin/theme conflicts, preferably in a staging environment.
If these steps do not resolve the issue, or if the problem seems complex, please do not hesitate 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.
Problem: The client is trying to manage translation settings using WPML and ACF Pro and wants to hide certain system fields from being translated. They are unable to hide specific fields from WPML translation as indicated in their screenshot and are looking for a way to configure this, preferably using XML, to easily transfer settings across different sites. Solution: We recommend removing the current XML configuration that is causing these fields to appear in the WPML Translation Editor. Instead, utilize the translation preference settings available in the field groups when the "Advanced Custom Fields Multilingual" plugin is active. For detailed guidance, please refer to our documentation here: https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/. Additionally, ensure that your XML config only includes keys for text strings that need translation and avoid including any style, settings, or data fields.
If this solution does not resolve your issue or 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 further assistance is needed, please open a new support ticket at https://wpml.org/forums/forum/english-support/.
Problem: The client is experiencing an issue with the core List block, where the translation does not appear as expected on their site when using WPML. The expected translation does not match what is displayed.
Solution: We resolved the issue by removing specific XML configuration that was not necessary for WPML to handle core blocks. Here are the steps to fix the issue:
1. Navigate to WPML -> Settings -> Custom XML Configuration.
2. Remove the following XML:
3. Save the changes. 4. Open your post or page with the List block in the default language and save or update the post/page. This should trigger the translation update. 5. If the update does not trigger, make a small change in the content and save again. 6. Update the translation in ATE, review, and hit "Complete translation" ensuring it is at 100%. 7. Repeat steps 3 to 6 for all posts/pages where this List block is used. 8. Clear all caches and check the frontend.
If this solution does not resolve your issue or seems outdated, please check related known issues, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If the problem persists, we recommend opening a new support ticket at WPML support forum.
Problem:
If you're experiencing issues with changing the translation engine in WPML from Deepl to Google and not seeing any changes in the translated content, or if you're curious about how WPML handles having both Google and Deepl translation engines enabled at the same time, we have some guidance for you. Solution:
For the first issue, ensure that you have completely deleted the previous translation from both the list where the page/post translation appears and from the trash. We have a guide on how to properly delete a translation: https://wpml.org/faq/how-to-delete-the-translation-of-a-page/. It's possible that the translation was not fully removed before resending the translation job with the new translation engine selection.
Please note that the solution provided might be irrelevant if it's outdated or not applicable to your case. If the issue persists, 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 don't hesitate to open a new support ticket with us.
Problem: The client was inquiring about how WPML handles having both Google and Deepl translation engines enabled at the same time. Solution: We explained that WPML prioritizes the translation engines based on the order of preference set by the client. The engine listed at the top will be used first, provided it supports the language pair required for the translation. If the top choice is not compatible, WPML will then attempt to use the second option, and so on. We recommended reviewing our documentation on how to change automatic translation engines for more detailed information: https://wpml.org/documentation/automatic-translation/how-to-change-automatic-translation-engines/
If this solution does not apply to your situation, or if it seems outdated, we encourage you 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: https://wpml.org/forums/forum/english-support/.
