marjolein64

We solved the issue! All is working as expected. When a visitor enters the checkout all payment methods are available now.
We had three duplicate shipping methods for pickup. I removed two of them, and now it is working. I don’t know why this solves the problem, but maybe someone will find this helpful.

I also installed this new beta version, but the message stating that no payment methods are available still appears when a customer enters the checkout. The customer first has to select the country (the only option is the Netherlands), and only then do the payment options appear. Customers will leave the checkout because they think they can’t complete their purchase!

In addition to my message above: it only works if the visitor is logged in or has selected a country. We only ship to the Netherlands, so this is confusing for the visitor. How can we ensure that all payment options are visible immediately?

We had similar issues. Even with the default theme and only the WooCommerce and Mollie plugins active, no payment options were available. My checkout page was in the classic format, so I recreated it to switch to the new format. However, it still didn’t work initially. After installing the beta version of Mollie, everything is working fine. I assume I can continue using this beta version for now?

Hi @ibrahimsharif ,

Thanks for your help!
Without making any changes, the email started working again in september without error messages.

Marjolein

Hi,

Thanks for your reply.
At this time, I’m not able to reproduce the fatal errors anymore. I’ll contact Pro support in case I need additional help, thanks.

Hi Jarno,

Yes, you are correct! I completely forgot that I had Complianz disabled. All is working now, thanks for your help!

marjolein

Hi Jarno,

Thanks for your reply.
You are right, I removed these files because of the fatal error.

Today, with all updates installed, I added the necessary files again to the mu-plugin folder, but I still have the same error:

Fatal error: Uncaught Error: Call to undefined function cmplz_get_cookiebanners() in /customers/a/d/7/wespenbestrijders.nl/httpd.www/wp-content/mu-plugins/banner.php:44 Stack trace: #0 /customers/a/d/7/wespenbestrijders.nl/httpd.www/wp-includes/class-wp-hook.php(324): regenerate_banner(”) #1 /customers/a/d/7/wespenbestrijders.nl/httpd.www/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array) #2 /customers/a/d/7/wespenbestrijders.nl/httpd.www/wp-includes/plugin.php(517): WP_Hook->do_action(Array) #3 /customers/a/d/7/wespenbestrijders.nl/httpd.www/wp-settings.php(695): do_action(‘init’) #4 /customers/a/d/7/wespenbestrijders.nl/httpd.www/wp-config.php(78): require_once(‘/customers/a/d/…’) #5 /customers/a/d/7/wespenbestrijders.nl/httpd.www/wp-load.php(50): require_once(‘/customers/a/d/…’) #6 /customers/a/d/7/wespenbestrijders.nl/httpd.www/wp-blog-header.php(13): require_once(‘/customers/a/d/…’) #7 /customers/a/d/7/wespenbestrijders.nl/httpd.www/index.php(17): require(‘/customers/a/d/…’) #8 {main} thrown in /customers/a/d/7/wespenbestrijders.nl/httpd.www/wp-content/mu-plugins/banner.php on line 44

Any idea what’s causing this?

Hi @wfphil,

Thanks for your reply.
I have sent the server logs to the e-mail address. In that e-mail, I have also added a screenshot of the WPML language settings.
As far as I know, we don’t run wp-cron.php from linux.

Yes, you are correct! I have an extra slash: …//wp-admin/…

When I perform a manual scan I’m able to see the results, I only have this issue when opening notifications from the Wordfence dashboard.
Switching to the other language has the same issue.

Thanks for your reply.

I just sent the diagnostics report to your e-mail

Hi Shameem,

YES, it’s solved now! Thank you so much!
The order attribution feature is causing the fatal error. After disabling this option all is working without errors.

Thanks again for all your help.
Marjolein

I have deactivated WP Acitvity Log and the Installatron plugin. But the fatal error is still there.
I already tried removing and reinstalling the Woocommerce plugin, but that didn’t help either.

Hi Pepe,

Thanks!
No, after the actions, the fatal error is still showing…

Hello Zubair Zahid,

I enabled High-performance order storage, but the fatal error is still showing in the order view.

I checked all the Woocommerce settings and they look fine. The only time we have this fatal error is in (single) order view.
I remember there were some issues when using a comma as the decimal separator after an earlier update. Is it possible that this is causing problems?

Thanks!