This thread is resolved. Here is a description of the problem and solution.
Problem: The client reported an issue where WooCommerce Subscriptions was not working correctly with WPML. The site's default language is English, but when attempting to edit a subscription, the backend would open in the user's language and display a blank page. Solution: 1. We asked the client to provide the error log. 2. After reviewing the log, we identified that the error originated from WooCommerce, specifically at
. 3. We advised the client to deactivate WPML plugins to check if the issue persists. 4. We then suggested that the client contact the WooCommerce support team and share the error log with them for further assistance.
Please note that the solution provided might be irrelevant due to being outdated or not applicable to your case. If the issue persists, we highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If necessary, do not hesitate to open a new support ticket with us for further assistance.
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.
WPML is not working correctly with Woocommerce Subscriptions. I have spoken to WS and they said the error is with your plugin.
Our site is default in English. When we go to edit a subscription, the subscription backend is opened in the users language and not english and is a blank page. I have attached a screenshot.
While waiting for one of my colleagues to help you, please review the following Errata documentation that might be related to the issue you are experiencing.
I'm Osama from WPML forums support. I'll be glad to help you today.
First of all, sorry for the late reply; it was due to a higher workload. Please provide me with the WordPress debug.log; this will allow us to see if any PHP errors are being produced. More Info: https://wordpress.org/support/article/debugging-in-wordpress/
To enable it, open your wp-config.php file and look for the following line:
define('WP_DEBUG', false);
And change it to:
define('WP_DEBUG', true);
// Enable Debug logging to the /wp-content/debug.log file
define('WP_DEBUG_LOG', true);
// Disable display of errors and warnings, which is recommended on a live site.
define('WP_DEBUG_DISPLAY', false);
@ini_set('display_errors',0);
Then try to reproduce the issue and check if any errors were saved to the debug.log log file inside the /wp-content/ directory.
If you can paste your debug.log to https://pastebin.com/ and provide me with that link, it would be great!
