Problem: If you're experiencing browser tab crashes or a squashed editor interface when using WPML and Classic Editor together, it might be due to a conflict with another third-party plugin. Solution: We recommend deactivating your third-party plugins one by one to identify which one might be causing the issue. This step-by-step approach helps isolate the problematic plugin. If the problem persists even after deactivating other plugins, or if this solution does not apply to your case, please check the related known issues and ensure you have the latest versions of themes and plugins installed. If you still need assistance, we encourage you to open a new support ticket with us for further help. You can do so here: WPML support forum.
Problem: You are working on a site under development and trying to export data to import it using WPML. However, you are unable to find an addon for WP All Export to facilitate exporting data for import. Solution: We recommend updating to the latest WPML version and checking if the issue persists. This should be fixed in the WP All Import Multilingual 2.3.1.
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 continues, please open a new support ticket at WPML support forum for further assistance.
Problem: The client was experiencing an issue where attempting to order a product with only 1 in stock resulted in an error, and it appeared as though two orders were created, but only one was processed in the admin. This occurred when WPML String Translation was enabled, and there was also a problem with the refund process when WPML Multilingual CMS was active. Solution: We identified a PHP fatal error related to a format specifier in the WooCommerce email notification system. The error was traced to a translation string for the 'out of stock' message in WPML String Translation, which had an incorrect format. We corrected the translation from "Níl stoc de % againn." to "Níl stoc de %s againn." and verified that the checkout and refund processes functioned correctly thereafter. For further details on this type of error, you can refer to the documentation at https://wpml.org/errata/php-8-php-fatal-error-uncaught-valueerror-unknown-format-specifier-in/.
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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: If you're experiencing issues where adding a WooCommerce shortcode breaks the page editing functionality, and you're unable to edit the page until you disable either WPML or WooCommerce plugins, the problem might be related to string translations. Solution: We recommend checking the WPML -> String Translation section for the specific string 'Select options for'. It's likely that the translation format is incorrect. You should change it from "%": Déan rogha to "%s": Déan rogha. This adjustment has been tested and should resolve the issue.
Regarding the removal of all current strings and using only .mo files, we advise against deleting strings from the String Translation as this will result in strings appearing untranslated. It's essential to have them registered within the String Translation screen for proper functionality.
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.
Problem: The client has numerous categories in a bilingual GA/EN setup, where categories are randomly set with their original language instead of all being set to GA as intended. Manually adjusting each category's original language for about 150 categories is impractical. Solution: We recommend the following steps to streamline the process of setting GA as the original language for all categories: 1. Delete the translations, keeping only the categories in the default language. 2. Create a dummy product and add all the categories to it. 3. Use the translation editor to translate these categories. If using the advanced translation editor and the categories were previously translated, they should appear translated. 4. Save the product to set GA as the default language for these categories. 5. Navigate to WooCommerce Multilingual > Categories, scroll to the bottom of the page, and click the button to synchronize the categories across all products. Before proceeding, ensure you back up your site and perhaps start with just one or two categories to familiarize yourself with the process and check for any unexpected issues.
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 WPML support forum.
Problem: The client wants to completely remove WPML and all associated data from their site to start over with a fresh installation, using .mo files for translations. Solution: We recommend following the detailed steps provided in our documentation to reset WPML. This process will help you remove WPML along with all saved settings and translations. You can find the guide here: Deleting Languages and Plugin Data by Doing a WPML Reset on Your Site. After resetting, you can start afresh with the proper setup using .mo files for translations. If you encounter any issues during this process or have specific strings that you cannot translate, please do not hesitate to open a new support ticket so we can assist you with that particular issue.
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 contact our support team for further assistance.
Problem: The client wants to completely remove WPML to start over on a website rebuild, but cannot find documentation on how to do so and has concerns about duplicate support tickets. Solution: If you're experiencing the need to completely remove WPML and restart your website, we recommend following the discussion and steps provided in the existing support ticket. You can find the necessary information and continue the conversation on this topic at https://wpml.org/forums/topic/i-would-like-to-completely-remove-wpml-so-i-can-start-again-but-properly-this-time/. Please avoid opening multiple tickets for the same issue as it can delay the response to your original query.
If this solution is 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. Should you need further assistance, please open a new support ticket at WPML support forum.
