Problem: If you're experiencing issues with invalid or duplicate GTIN, UPC, EAN, or ISBN errors in WooCommerce after integrating with Google, particularly when creating products in a non-English language, you're not alone. This problem arises during the inclusion of new products, updating product stock, and making adjustments in product descriptions. Solution: We have replicated this issue and reported it to our development team for resolution in a future release. Although the error message appears, please note that all updated data in the product is still saved successfully when you click Update. The GTIN code is also correctly displayed in the database for both the original and translated products. A fix for this issue is confirmed to be included in one of the upcoming updates.
Please be aware 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 problem persists, please open a new support ticket.
Problem: The client is experiencing a website crash when updating product information on a WooCommerce site, accompanied by an error message from the WPML Multilingual CMS plugin indicating a type E_ERROR on line 657 in
. The error message states: 'Uncaught Error: Cannot use object of type WP_Error as array'. Solution: If you're encountering a similar issue, we recommend the following steps: 1. Navigate to WPML → Support → Troubleshooting. 2. Click on the following options one by one: - Remove ghost entries - Set language information Please ensure to back up your database before making any changes.
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. Additionally, you can open a new support ticket for further assistance at WPML support forum.
Problem: The client experienced a crash in their webshop after attempting to install WPML for the first time. The crash was accompanied by multiple PHP Deprecated warnings and a PHP Fatal error related to an empty string for the language code. Additionally, after resolving the initial crash, WPML did not translate the root page of the site. Solution: To address the crash and PHP errors: 1. We recommended resetting WPML completely. This involves going to WPML → Support, clicking the Troubleshooting link, and in the Reset section, selecting the 'I am about to reset all translation and language data' checkbox, then clicking the 'Reset and deactivate WPML' button. 2. If the problem persists, we suggested sharing wp-admin and FTP access to a staging site for further investigation. To resolve the issue with the untranslated page: 1. We advised checking if the Divi Templates were translated. This can be done by going to WPML > Translation Management > Dashboard, creating a job for each template, sending them to automatic translation or assigning the jobs to yourself, and then accessing them at WPML > Translations to translate them with the WPML Translation Editor.
If these solutions do not resolve your issues or seem 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 problems persist, please open a new support ticket.
