Problem: The client was experiencing an error message after updating WPML, stating that the WordPress REST API must be enabled, despite it being accessible. The issue was compounded by hosting restrictions that blocked certain countries, potentially affecting the REST API's functionality. Solution: 1. We advised the client to contact their hosting provider to check access permissions to their site. 2. We suggested temporarily disabling any restrictions, flushing any cache, and then checking if the issue was resolved. 3. We recommended that the client ask their hosting provider to whitelist wpml.org and ate.wpml.org. 4. We confirmed that it was acceptable to temporarily activate plugins that might be blocking communication with our servers, but to be aware that these could be causing the issue. 5. We clarified that WPML needs to communicate with our servers for managing translations and updates, which is normal for large WordPress plugins. It's not necessary to remove all restrictions, just those that prevent communication with WPML servers.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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: As a site admin, you're finding it difficult to edit product translations in WPML. After selecting a product in WPML > Translation Management, you're unsure how to proceed with translating it. Additionally, sometimes the WPML Advanced Translation Editor (ATE) shows the translated content as empty even though it exists on the front end. Solution: This issue arises due to how WPML's translation memory utilizes fuzzy matching. When you update the original content, WPML attempts to match the new content with existing translations. If the changes are significant, or if a close match isn't found, the ATE may display the translation fields as empty, requiring a re-translation of the content. This is to prevent inconsistencies in translations. For more detailed information, please visit how WPML keeps track of your translations.
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. For further assistance, please visit our support forum.
Problem: You are using WPML to translate your website and are experiencing issues with the Arabic and Hebrew languages. The related product slider works fine in English but breaks when switching to Arabic or Hebrew. The issue persists even after disabling all plugins, including WPML, leading you to suspect an incompatibility between WPML and the mini cart or the theme. Solution: Since the problem occurs even when WPML is disabled, it suggests that the issue is not related to WPML. We recommend contacting the theme support to investigate further, as the issue might be related to theme compatibility with RTL (Right-to-Left) and LTR (Left-to-Right) languages. Show them that the issue happens without any additional plugins and ask for their assistance.
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 the problem persists, please open a new support ticket at WPML support forum for further assistance.
