Home›Support›English Support›[Resolved] WooCommerce Multilingual & Multicurrency plugin is causing an issue
[Resolved] WooCommerce Multilingual & Multicurrency plugin is causing an issue
This thread is resolved. Here is a description of the problem and solution.
Problem:
You are experiencing a blank settings page for WooCommerce Product Options due to a JavaScript error caused by the WooCommerce Multilingual & Multicurrency plugin.
Solution:
This issue is occurring due to a compatibility conflict with the WooCommerce Product Options plugin by Barn2 Plugins.
It will be resolved by upgrading to the beta version of the upcoming WPML 4.8 series and version 5.5.2 of WooCommerce Multilingual, which includes a fix for this issue. Check the following links for more details on the beta version and changelogs:
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. Also, check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. For further assistance, please visit our support forum at WPML Support Forum.
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 am trying to update the setting for WooCommerce Product Options, but the settings page is blank. I have raised this with Barn2, the plugin provider, and they have identified a JavaScript error being caused by the WooCommerce Multilingual & Multicurrency plugin. They have identified this issue and provided an image: hidden link and tested on our development site: hidden link. The issue can be seen on this page: hidden link.
Symptoms:
The settings page for WooCommerce Product Options is blank instead of displaying the option settings.
Questions:
What is causing the settings page to be blank?
How can I resolve the JavaScript error identified by Barn2?
Welcome to the WPML support forum. I will do my best to assist you in resolving the issue.
This may be a compatibility issue. Therefore, please share the WordPress debug.log (not WPML debug information) with us so we can collect more details on this. Refer to the following links for instructions
To enable WordPress Debug log, open your wp-config.php file of the site root and look for define('WP_DEBUG', false);. Change it to:
// Enable WP_DEBUG mode
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
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );
In this case, the errors will be saved to a debug.log log file inside the */wp-content/* directory. Please do the steps to reproduce the bug and check if you are getting any errors or warnings related to WPML in the log file.
If you can paste your debug.log to http://pastebin.com/index.php and provide me with that link, it would be great! (This is the cleanest way because sometimes the logs are long and create a complete mess of discussion.)
Hi I did email back on 25th, but it does not seem to have updates this log? This is now quite critical for us. My email said:
Hi Bigul, We’ve done that, and gone to the problem page, but no debug or php errors are being generated.
Would it help if I gave you access to our development site, so you can see the issue for yourself?
Thank you for the updates. Please note that our support is limited to this forum, so the email you sent will not be added to the forum. Kindly continue the conversation here so we can assist you more effectively.
Please fill in the private details fields (including the FTP credentials) after a full site backup. I would like to access the admin area of your staging site for further checking. Refer to the following links for more details about our private information sharing policies.
Thank you for the updates. Please note that our support is limited to this forum, so the email you sent will not be added to the forum. Kindly continue the conversation here so we can assist you more effectively.
Please fill in the private details fields (including the FTP credentials) after a full site backup. I would like to access the admin area of your staging site for further checking. Refer to the following links for more details about our private information sharing policies.
Thank you for the login information and the details. I can reproduce the issue on your staging site.
This requires further testing. So, please grant permission to:
- Deactivate non-WPML plugins (in hidden link)
- Switch to the default Twenty Twenty-Five theme on the staging site for further troubleshooting
- Create a copy of the site using the Duplicator plugin in case of escalation to our developers
Thank you for the permission. I performed a few rounds of testing on your staging site, but the issue persists even after the initial troubleshooting steps. It only works as expected when WooCommerce Multilingual is reactivated.
I have made a copy of the site for detailed debugging and escalation to our second-tier team. We will get back to you as soon as possible with further updates. Please wait.
I am getting the expected results on both my local copy and your staging site after upgrading to the beta version of the upcoming WPML 4.8 series, which is currently in the final stage of QA.
hidden link
The fix for this bug is included in version 5.5.2 of WooCommerce Multilingual. Please refer to the attached screencast for more details.
Please check your staging site and let us know your feedback.
Thank you for the confirmation. WPML 4.8 is currently in its final stage of development and is expected to be released in the coming weeks. The beta version is already available for download and testing.
Please refer to the following links for more details.
