Fatal error with 4.4.17 – CompatibilityChecker::make()

Resolved

(@josklever)

After updating to version 4.4.17 on a website it crashes with the following error:

PHP Fatal error:  Uncaught Error: Call to undefined method Mollie\Api\CompatibilityChecker::make() in /.../wp-content/plugins/paytium/libraries/Mollie/vendor/mollie/mollie-api-php/src/MollieApiClient.php:155
Stack trace:
#0 /.../wp-content/plugins/paytium/class-paytium.php(683): Mollie\Api\MollieApiClient->__construct()
#1 /.../wp-includes/class-wp-hook.php(341): Paytium->includes()
#2 /.../wp-includes/class-wp-hook.php(365): WP_Hook->apply_filters()
#3 /.../wp-includes/plugin.php(522): WP_Hook->do_action()
#4 /.../wp-settings.php(742): do_action()
#5 /.../wp-config.php(96): require_once('...')
#6 /.../wp-load.php(50): require_once('...')
#7 /.../wp-blog-header.php(13): require_once('...')
#8 /.../index.php(17): require('...')
#9 {main}
  thrown in /.../wp-content/plugins/paytium/libraries/Mollie/vendor/mollie/mollie-api-php/src/MollieApiClient.php on line 155

WordPress 6.9
PHP 8.2

Viewing 13 replies - 1 through 13 (of 13 total)

Plugin Author paytiumsupport
(@paytiumsupport)

3 months, 1 week ago

Hi Jos,

Thanks for reaching out .

For now pls fall back to 4.4.16 where it did work and mail us @ support@ paytium.nl

Paytium support team

Thread Starter Jos Klever
(@josklever)

3 months, 1 week ago

I’ve already sent an email, directly after creating this post. It was just answered by asking for my admin credentials on the website and I explained that you shouldn’t ask for that and what should be done.

Plugin Author paytiumsupport
(@paytiumsupport)

3 months, 1 week ago

Hi Jos,

We have replied to your email with our diagnostics.

Please feel free to send us your site diagnosis results, so we can pinpoint exactly where the conflict arises.

Paytium support team

Plugin Author paytiumsupport
(@paytiumsupport)

3 months, 1 week ago

Hi Paytium 4.4.17 users,

Paytium plugin version 4.4.17 has been tested on a completely clean install of WordPress

WordPress 6.8 up to and including WordPress 6.9 and PHP 8.1 up to and including PHP 8.4 with version 4.4.17.

If you experience any issues in site environment-

Please perform a short site diagnosis by – deactivating all Plugins except Paytium plugin / Temporarily activating default WordPress theme , in order to exclude first own site environment – theme, hosting configuration or other plugins

Please send us your site diagnosis results, do include error notice text, if issue still appears.

Thank you,

Paytium support team

bramdehaan
(@bramdehaan)

3 months, 1 week ago

I can confirm the issue posted by @josklever , website crashed after installing vs. 4.4.17. Solved when reinstalling vs. 4.4.16

Please perform a short site diagnosis by – deactivating all Plugins except Paytium plugin / Temporarily activating default WordPress theme , in order to exclude first own site environment – theme, hosting configuration or other plugins

Website was working fine … so why would I want to go through all this trouble if the issue is clearly with the new version of this plugin?

Thread Starter Jos Klever
(@josklever)

3 months, 1 week ago

I suspect that Mollie Payments for WooCommerce might be the plugin that has a conflict with the new Mollie API from Paytium. I’ve already emailed back to check that. Otherwise it would be a lot of extra work to create a staging file and investigate this issue as it’s not possible to perform the advised tests on the live website without breaking the site completely for visitors.

@bramdehaan Are you using Mollie Payments for WooCommerce 8.1.1 on this site as well?

bramdehaan
(@bramdehaan)

3 months, 1 week ago

Indeed, yes @josklever I am using Mollie Payments for WooCommerce 8.1.1 as well. Just tested this on my local dev. env. Have the latest version of Paytium running on this local development environment with Mollie Payments for WooCommerce de-activated for obvious reasons, and the local site works fine but crashes when activating the MPfWC plugin. So I can confirm this conflict as well.
Daniël
(@devdaniels)

3 months, 1 week ago
We experienced the same issue. We have automatic updates on minor updates on, which broke the website without us knowing. I won’t not expect a minor update to break the website.

Turning the plugin Mollie Payments for WooCommerce off did the trick. Luckily we didn’t use that plugin. Apparently one plugin can interfere with another plugin. After disabling the Mollie Payments for WooCommerce plugin we could safely update the Paytium Plus plugin.

Also mail support of @paytiumsupport asking for admin login details is not a professional way to work… This damages the trust.
- This reply was modified 3 months, 1 week ago by Daniël.
ldwd
(@ldwd)

3 months ago

We encountered the same issue: updating to 4.4.17 with Mollie Payments for WooCommerce enabled caused a fatal error.

At first we didn’t know what caused it. By disabling all plugins via the database we gained access to the back-end again. While re-enabling the plugins it crashed again on activating Mollie Payments for WooCommerce. Looking in our update history, the last plugin updated before the first crash was Paytium (Mollie’s last update was from a month ago, so that couldn’t be it). Checking this forum I saw similar reports. Reverted back to 4.4.16 and all works fine.

So yes, most definitely there is a conflict with Mollie Payments for WooCommerce 8.1.1.
We use WP 6.9.

Thread Starter Jos Klever
(@josklever)

3 months ago

I’ve just asked support for an update, since it had been 1 week without any reply. They did reply now, but only could mention that they are working on it and a rollback to 4.4.16 is the only workaround for now.

ldwd
(@ldwd)

3 months ago

@josklever Thank you for your update, that’s very kind 🙂
We’ll be waiting for their fix.

Thread Starter Jos Klever
(@josklever)

2 months, 3 weeks ago

I’ve just updated to version 5.0.0 and I don’t see an error anymore, so it’s solved!

I still haven’t received a reply on my ticket (via email) since 6 days. Hopefully you want to listen better to feedback and test results in the future, so we can get to a solution sooner.
uwtopwhisky
(@uwtopwhisky)

1 month ago
Okay, I mailed them the day the update came in that there was a problem and they told me I had to contact the conflicting plugin owner. Then i found out it was Mollie so I was a bit confused but cause it was december I had to deactivate Paytium. Now I have time again so I asked them again but they came up with an answer which told me I am the very first with this………………….. So no.

Version 5.0.0 solves the problem, let’s find it.

Okay 5.0.1 it is, and this paytium plus user had to solve it thanks to you guys, tnx
- This reply was modified 1 month ago by uwtopwhisky.

Viewing 13 replies - 1 through 13 (of 13 total)

You must be logged in to reply to this topic.