[Resolved] fatal error using WooCommerce Multilingual & Multicurrency
This thread is resolved. Here is a description of the problem and solution.
Problem:
The client experienced a fatal error when switching to English to create posts in WordPress, causing the site and dashboard to crash. This issue occurred when both WooCommerce Multilingual & Multicurrency and WooCommerce PayPal Checkout Gateway plugins were active.
Solution:
We identified that the issue was due to a compatibility problem between WooCommerce PayPal Checkout Gateway and the Classic Editor plugin. To resolve this, we recommended:
1. Keeping the Classic Editor plugin active. 2. Ensuring that WooCommerce PayPal Payments is updated and configured correctly, replacing the unsupported WooCommerce PayPal Checkout Gateway. 3. Upgrading to the latest version of WooCommerce Multilingual & Multicurrency, which includes improvements that might resolve the issue. 4. Testing the site after these adjustments to confirm if the fatal error is resolved.
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 the problem persists, please 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.
Thanks for the update. I have checked the backend again, and while I was able to create new products in both Japanese and English, I'm still getting the same error message when I try to create new portfolio or new post items in English. The mail that comes with the error message shows as follows:
Error Details
=============
An error of type E_ERROR was caused in line 147 of the file /home/customer/www/staging6.izanami-wheel.com/public_html/wp-content/plugins/woocommerce-multilingual/classes/multi-currency/payment-gateways/class-wcml-currencies-payment-gateways.php. Error message: Uncaught Error: Call to a member function get_setting() on null in /home/customer/www/staging6.izanami-wheel.com/public_html/wp-content/plugins/woocommerce-multilingual/classes/multi-currency/payment-gateways/class-wcml-currencies-payment-gateways.php:147
Stack trace:
#0 /home/customer/www/staging6.izanami-wheel.com/public_html/wp-includes/class-wp-hook.php(324): WCML_Currencies_Payment_Gateways->filter_gateway_description('Pay via PayPal.', 'ppcp-gateway')
#1 /home/customer/www/staging6.izanami-wheel.com/public_html/wp-includes/plugin.php(205): WP_Hook->apply_filters('Pay via PayPal.', Array)
#2 /home/customer/www/staging6.izanami-wheel.com/public_html/wp-content/plugins/woocommerce/includes/abstracts/abstract-wc-payment-gateway.php(381): apply_filters('woocommerce_gat...', 'Pay via PayPal.', 'ppcp-gateway')
#3 /home/customer/www/staging6.izanami-wheel.com/public_html/wp-content/plugins/woocommerce-paypal-payments/modules/ppcp-settings/src/Data/Definition/PaymentMethodsDefinition.php(110): WC_Payment_Gateway
With the current theme in place, if I turn off the plugin "Woocommerce Multilingual and Multicurrency", I can again create new portfolio and posts in English and Japanese both smoothly. When I turn the plugin back on again, the error occurs and I can't proceed to the create post screen. When I tried running a default theme, I have the same result: able to create new posts/portfolio items in English only with the plugin switched off.
Thank you for the details. However, I am currently unable to reproduce the issue on my end. Everything appears to work as expected when I tried the following steps. Refer to this screencast for more information: hidden link
- Create a Blog Post or Portfolio Post in English
- Translate a Blog Post or Portfolio Post from Japanese to English
To help us investigate further, could you please share the exact steps to replicate the bug on your site?
I have referred to your screencast, but I'm not seeing the same thing on my end.
When switched to Japanese, I can create and edit all three types: product, post and portfolio item.
But when switched to English, I still cannot create or edit any post or portfolio items. I can however create and edit woocommerce products in English now.
I have tried on multiple devices and browsers, but get the same result as above each time.
Link to an upload of my screen capture video here:
^ In addition to the above, if I deactivate Woocommerce Multilingual and Multicurrency, I can create and edit posts/portfolio entries in English. Sorry, this part was not shown in the screencapture video.
Thank you for the updates. That sounds strange. Could you please try logging in with a different Admin user account and check if the issue still occurs?
If it works, please go to WPML >> Translation Management >> Translators tab, remove all the existing translators, and add them again. Then check whether the problem remains or not.
I logged in as guest, the same admin as passed to you, and I could create and edit posts and portfolio items the same as you.
Then, I navigated to WPML >> Translation Management >> Translators, and as per your instructions, I removed all translators and then added them back in as shown in the attached screenshot.
After that, I checked that creating and editing posts/gallery entires was still possible under the guest admin. It was operating smoothly.
Then, I logged back into my own account and tried to create and edit posts/gallery entries. Still getting the same error as previously, and could not access them.
Seems so strange that only the guest admin can create or edit posts when the settings are all the same for each account.
I created a new admin ID and I can operate everything normally from that ID now.
However, logging into my original admin ID, I still could not create or edit posts/portfolio items from that ID.
Similarly, from any admin ID on the main site, I could not update the woocommerce plugin to the latest version without getting a fatal error and needing to revert to a previous backup to access the dashboard. I tried deactivating "Woocommerce Multilingual and Multicurrency" plugin, then updating woocommerce to the latest version and this worked.
I'm not sure about the ongoing issues related to this plugin, but for now the post/portfolio issue is resolved with the new admin ID.
Using the newly created admin account, I can now create new posts and gallery items in English, but when I try to edit any existing posts or gallery items in English, the same error as before occurs.
This one:
Error Details
=============
An error of type E_ERROR was caused in line 147 of the file /home/customer/www/izanami-wheel.com/public_html/wp-content/plugins/woocommerce-multilingual/classes/multi-currency/payment-gateways/class-wcml-currencies-payment-gateways.php. Error message: Uncaught Error: Call to a member function get_setting() on null in /home/customer/www/izanami-wheel.com/public_html/wp-content/plugins/woocommerce-multilingual/classes/multi-currency/payment-gateways/class-wcml-currencies-payment-gateways.php:147
Stack trace:
#0 /home/customer/www/izanami-wheel.com/public_html/wp-includes/class-wp-hook.php(324): WCML_Currencies_Payment_Gateways->filter_gateway_description('Pay via PayPal.', 'ppcp-gateway')
#1 /home/customer/www/izanami-wheel.com/public_html/wp-includes/plugin.php(205): WP_Hook->apply_filters('Pay via PayPal.', Array)
#2 /home/customer/www/izanami-wheel.com/public_html/wp-content/plugins/woocommerce/includes/abstracts/abstract-wc-payment-gateway.php(381): apply_filters('woocommerce_gat...', 'Pay via PayPal.', 'ppcp-gateway')
#3 /home/customer/www/izanami-wheel.com/public_html/wp-content/plugins/woocommerce-paypal-payments/modules/ppcp-settings/src/Data/Definition/PaymentMethodsDefinition.php(110): WC_Payment_Gateway->get_description()
#4 /home/customer/www/iza
By deactivating the "Woocommerce Multilingual and Multicurrency" plugin, I receive no error message when try to open and edit those posts.
Thank you for the updates. We will make a new copy of the site and perform a detailed debugging.
One request: Could you please share the credentials of an admin user who is experiencing issues while creating Posts and Products in English? This will help us cross-check and reproduce the problem more accurately.
Thank you for the updates. Just to confirm, is the admin user iz****in2 a newly added account?
If possible, please share the credentials of the original admin user who is experiencing issues with creating posts. This will help us troubleshoot all the related cases more effectively.
I have enabled the private option for your next reply to ensure secure sharing.
Thank you for the details and login information. This looks like a compatibility issue and requires further checking. So I made a copy of the site using Duplicator after upgrading to the latest version of the plugins, and will debug it locally and get back to you soon. Please wait.
I have run several rounds of testing in our local environment, but couldn’t reproduce the issue exactly. So, I attempted to replicate it on your staging site: hidden link
Everything works as expected in a minimal setup on your staging site, with only the WPML plugins, WooCommerce, and the Virtue - Premium parent theme active.
Therefore, please check whether the issue still occurs in this minimal setup. This will help us identify if another plugin or customization is causing the conflict.
Please try it and let us know your feedback. Thank you for your kind understanding.
Thanks for your continued support with this issue.
I have checked the staging site in minimal setup as you specified. I can open and edit posts and portfolio items smoothly.
One thing that I have noticed that appears differently is that when the option to select "edit - block editor" and "edit - classic editor" in English, the error occurs.
When (as currently shown on staging site in minimal setup) there is no option to select between block/classic editor, then there is no error.
I'm not sure if this could be connected to the problem, but I just wanted to bring that to your attention. I attached a screenshot comparing these two cases here. Please let us know if you have any updates.
Thank you.
Manage Cookie Consent
We use cookies to optimize our website and services. Your consent allows us to process data such as browsing behavior. Not consenting may affect some features.
Functional
Always active
Required for our website to operate and communicate correctly.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
We use these to analyze the statistics of our site. Collected information is completely anonymous.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
These cookies track your browsing to provide ads relevant to you.
