Problem: The client was unable to translate some text on the WooCommerce checkout page using WPML. Despite adding XML to the custom XML configuration setting as suggested by other tickets, the issue persisted. Some text was not found in the string translator, and some translated text still appeared in English. Solution: We accessed the staging site and created a new Cart page using the WooCommerce shortcode
[woocommerce_cart]
, which resolved the translation issue for the Cart page. For the checkout page, we identified and corrected the use of an incorrect shortcode. We recommend the client to verify the changes on the French checkout page.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please visit our support forum to open a new 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: You have a custom role setup and need to allow this role to edit translations for their own content in WPML. Solution: We recommend adjusting the capabilities for your custom role to include permissions to translate and manage translations. Specifically, you should set this role as a translator. For detailed guidance on how to adjust these capabilities, please refer to the following documentation:
If this solution does not fully address 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 do not hesitate to open a new support ticket at WPML Support Forum.
Problem: The client is experiencing an issue where courses can be published without filling in all required fields when WPML is enabled. This problem does not occur when WPML is disabled. Solution: We recommend updating Advanced Custom Fields (ACF) to the latest version as a similar issue with field validation was resolved in that update. You can find more information on this update here: Advanced Custom Fields conflicts with field validation on AJAX requests. Additionally, it is not necessary to translate custom fields groups with ACFML. Therefore, you can set ACF custom fields to be not-translatable in WPML->Settings->Post types translations, which allows you to manage fields from one place rather than two. For more details on managing ACF with WPML, visit: Translate sites built with ACF.
If this solution does not resolve your issue or seems irrelevant due to being 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client has a custom user role on their site and needs this role to be able to edit all translations. They encountered an issue where the custom role could edit some but not all translations, and assigning the role of translator and translation manager did not resolve the issue. Solution: 1. We recommended checking the workaround provided in our documentation: WPML custom role based on the editor role cannot edit translations and behave as editor. 2. We also informed the client that WPML 4.6.9 has been released, which includes a fix for this issue. We advised updating WPML to the new version to resolve the problem.
