Problem: The client experienced performance issues with their webshop when using WPML and WCML's currency switcher. They are considering using a lightweight currency switcher, specifically Curcy Pro (paid version), and need to know if it is compatible with WPML without causing performance degradation. Solution: We recommend contacting Curcy's support service to confirm if their plugin is compatible with WPML. Additionally, you can refer to a related issue discussed in our forums: https://wpml.org/forums/topic/after-changing-to-other-currency-cant-change-back-to-default-currency-usd/ which was resolved by LiteSpeed developers.
Please note that the solution provided 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: If you're using BeTheme with WPML and notice that English posts display the excerpt correctly above the featured image, but German posts translated via WPML do not show the excerpt (the wrapper gets class no_content and is empty), even though the excerpt is saved correctly in the database. Solution: We recommend following these steps to resolve the issue: 1. Ensure that the BeTheme template is fully translated and synchronized. This was the root cause in a similar case. 2. Check the BeBuilder data storage settings and ensure they are set to 'Serialized', and that 'mfn-page-items' is set to 'Translate' in WPML Custom Fields. 3. Visit the documentation on making BeTheme content available for translation. If these steps do not resolve the issue, it 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.
Problem: After migrating a site from a staging environment to production, the Advanced Translation Editor (ATE) cloud was rejecting all translation jobs with an HTTP 426 error, indicating a URL change. The client attempted various troubleshooting steps, including reactivating WPML plugins and confirming site key registration, but the issue persisted. Solution: We recommended the client to re-save the original pages in the default language (DE) to refresh the database entries. This action allowed the ATE to recognize the correct production URL and accept translation jobs. The client confirmed that after re-saving the affected pages and updating the translations, the issue was resolved.
If this solution does not apply to your case, or if it seems outdated, please check the related known issues and confirm that you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket at WPML support forum.
Problem: The client reported that although the plugin strings are fully translated into Hebrew, some strings are not displayed in the backend of the Amelia plugin. Even though these strings appear translated in the string translator, they need to be manually saved again to be visible. Solution: We recommended the client to provide examples of strings that are translated but not showing. This would allow us to investigate further and identify whether the issue is with the string translation saving process or another aspect of the plugin's integration with WPML. If the strings are not appearing in the string translator, it might indicate that the plugin's files need to be updated by the plugin author to ensure compatibility with WPML.
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.
