Home›Support›English Support›[Resolved] WPML String Translation plugin causes critical error for part of one category Woocomerce product lin...
[Resolved] WPML String Translation plugin causes critical error for part of one category Woocomerce product lin...
This thread is resolved. Here is a description of the problem and solution.
Problem: After updating WPML and other plugins, a critical error occurs on some WooCommerce product pages when the WPML String Translation plugin is active. Deactivating the plugin resolves the issue temporarily. Solution: To permanently fix the issue, modify the code in two files: 1. Navigate to
After making these changes, save the files. This solution was successfully applied to a staging site, resolving the issue.
Please note that this solution might be outdated or not applicable to your specific case. If the problem persists, we highly recommend checking related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If needed, do not hesitate to open a new support ticket.
This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
Background of the issue:
I updated my site with all the available updates, including WPML. After the update, I discovered that some of the products on the single product page are not opening, and there is a critical error message. I found that uninstalling the WPML String Translation plugin resolves the issue, and the products open correctly. For example, this product: hidden link works fine when the plugin is deactivated.
Symptoms:
Critical error on some WooCommerce product links when WPML String Translation plugin is active.
Questions:
How to solve the critical error caused by the WPML String Translation plugin?
Please follow these steps to obtain more information regarding the cause of the error:
- Create a full site backup
- Activate the WordPress debug mode as described in this link: https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/
- Reproduce the fatal error
- Share the fatal error message that appears in the browser or the debug.log file located within the wp-content folder
Hope I did as requested..
See error message attached.
P.s. I see that there is written something about elementor.. Just want to mention I have newest versions of WPML and Elementor and everything else is up to date as well..
The most likely cause of this issue is that the _elementor_data field is null or contains invalid data. I kindly ask you to follow these steps and let me know the results:
- Edit the hidden link product using Elementor
- Make a small change in the content
- Save the changes and update the translation
I updated content. Saved the changes. Cleared cache as well. Still the same problem. :/
And there is NO translation for products - so I can't update translation for product content. Website is just in one language. WPML is used just for string translation to Latvian (like Woocomerce Description -> Apraksts, Addidional information-> Tehniskie dati, HOME-> Sākums etc.)
And as I told before - if deactivate WPML String Translation plugin the problem is gone and everything works perfectly, but in this case all the strings are not translated - and it is not acceptable. This is the reason why I need WPML - to localize all page in Latvian.
Although the problem disappears when the String Translation plugin is deactivated, the cause of the issue is not the String Translation plugin.
Can you share the access credentials to the site in your next message so I can take a closer look? I have set your next message private so you can share the credentials securely.
Confirm you have a full site backup that you can restore if necessary.
I ran several troubleshooting steps, but the issue persists. Can you create a staging site with a copy of the live site where we can run further tests without affecting the live site?
You next message will be private so you can share the access credentials to the staging site securely.
