Error opening ‘bestellingen’ in woocommerce

Hey there @sanctibrouwer ,

My apologies for the late reply.
To learn more about this error we would like to ask you to open a support ticket with us directly on our website. Click here to learn how to contact us directly.
Please include your WooCommerce system report and any additional log files (server/PHP) that may show anything related to your update.
Thanks!

Kind regards,
Niklas

Hey there @sanctibrouwer ,

Thanks for your patience while we work on this case.
We have identified the issue and are preparing an update. It will likely be available sometime early next week.
The issue is a version conflict between GuzzleHttp version 6 and 7.
We found that one plugin potentially causing this conflict was WooCommerce Bookings.
If you disable either mollie or WooCommerce Bookings, you will see that you can access your WooCommerce settings again. If you encounter this issue and do not have WooCommerce Bookings installed, please contact us by clicking on this link.

Our plugin will soon be updated to prevent this conflict in the future. We will notify you as soon as the new update is available.

Kind regards,
Niklas

Hey there @sanctibrouwer ,

Thanks for your patience! We now have a stable but temporary workaround until our next regular update.
Please deactivate mollie Payments and then install this package. This link will be removed once the update is released.

Please keep the normal mollie Payments plugin deactivated until the next regular update. That’s when we will include a code refactor to permanently resolve conflicts like this.
When the next update is available, please remove the test package and update the normal mollie plugin instead.

If you have any other questions please do not hesitate to reach out.

Kind regards,
Niklas

Hello,

Thanks for the reply. And yes I’m indeed using this plugin. The update is still not live. Any ETA when this will be deployed?

Thanks,
Andre

Hello @sanctibrouwer,

We are still working on it. I cannot give you any specific time frames, but it should not be too far in the future. We are implementing this change in a variety of plugins, that’s why it took a little bit longer to plan.
In the meantime we were able to temporarily resolve these issues either by downgrading mollie to version 5.8.3 or by using our test package. Can you please let me know if either of these options worked for you as well?
As soon as our next update is available, I will notify every thread related to this issue.
Thank you for your patience!

Kind regards,
Niklas

Well since ‘your’ plugin the te payment plugin, I am not really eager to test this ?? So for now I just did not update woocommerce and the woocommverce bookings plugin. And now it seems all ‘okay’.

Where can I download your test version? I could not find that. Looking forward to a ‘real’ solution (just like you I can imagine:))

Hello @sanctibrouwer,
I linked the test package in my third answer in this thread.
Here it is:
https://drive.google.com/file/d/1f3oZxRQNTju3ehzHe65IngLkdrnvo86y/view

We are currently preparing our next release which is planned for early next week.
But since the fix for this issue is more complex than anticipated, we were not able to include our final implementation in this next update and will push it as an additional update later on.
So for now and a short period after our next update, we still recommend using either Mollie 5.8.3 or our test package linked above if you rely on WooCommerce Subscriptions.
I will update this thread as soon as we have a better solution.

Hey, I tried your newest one, and the old one from this topic:

newest version: Error on the payment page

Fatal error: Uncaught Error: Undefined class constant ‘VERSION’ in /home/blabla/domains/blabla/public_html/wp-content/plugins/mollie-payments-for-woocommerce/vendor/mollie/mollie-api-php/src/MollieApiClient.php:287 Stack trace: #0 /home/blabla/domains/blabla/public_html/wp-content/plugins/mollie-payments-for-woocommerce/src/Mollie/WC/Helper/Api.php(45): Mollie\Api\MollieApiClient->__construct() #1 /home/blabla/domains/blabla/public_html/wp-content/plugins/mollie-payments-for-woocommerce/src/Mollie/WC/Helper/Data.php(341): Mollie_WC_Helper_Api->getApiClient(false) #2 /home/blabla/domains/blabla/public_html/wp-content/plugins/mollie-payments-for-woocommerce/inc/utils.php(116): Mollie_WC_Helper_Data->getApiPaymentMethods(false, true) #3 /home/blabla/domains/blabla/public_html/wp-content/plugins/mollie-payments-for-woocommerce/src/Mollie/WC/Gateway/Abstract.php(2100): mollieWooCommerceAvailablePaymentMethods() #4 /home/blabla/domai in /home/blabla/domains/blabla/public_html/wp-content/plugins/mollie-payments-for-woocommerce/vendor/mollie/mollie-api-php/src/MollieApiClient.php on line 287

old version from the zip:

Error on the homepage (admin not even working) AND:

Fatal error: Uncaught Error: Call to undefined function GuzzleHttp\Psr7\uri_for() in /home/blabla/domains/blabla/public_html/wp-content/plugins/woocommerce-bookings/vendor/guzzlehttp/guzzle/src/Client.php:63 Stack trace: #0 /home/blabla/domains/blabla/public_html/wp-content/plugins/woocommerce-bookings/vendor/google/apiclient/src/Google/Client.php(1168): GuzzleHttp\Client->__construct(Array) #1 /home/blabla/domains/blabla/public_html/wp-content/plugins/woocommerce-bookings/vendor/google/apiclient/src/Google/Client.php(1123): Google_Client->createDefaultHttpClient() #2 /home/blabla/domains/blabla/public_html/wp-content/plugins/woocommerce-bookings/vendor/google/apiclient/src/Google/Client.php(392): Google_Client->getHttpClient() #3 /home/blabla/domains/blabla/public_html/wp-content/plugins/woocommerce-bookings/vendor/google/apiclient/src/Google/Client.php(871): Google_Client->authorize() #4 /home/blabla/domains/brouwerijegmond.n in /home/blabla/domains/blabla/public_html/wp-content/plugins/woocommerce-bookings/vendor/guzzlehttp/guzzle/src/Client.php on line 63

• This reply was modified 4 years, 4 months ago by sanctibrouwer.

anyone?

Hello @sanctibrouwer,

My apologies for the delay regarding this issue.
There was a bug in a package which we have to utilise to resolve this behavior and had to wait for it to be fixed ourself.
This means that our latest version 5.11.0 did not fix the conflict with WooCommerce Bookings just yet.
However, our next release should include our fix. I can’t tell exactly when it will be released, but as mentioned before I will update this thread once we have a final solution for this.
Thanks for hanging in there with us!

Kind regards,
Niklas

Hey. Is version 6.0 fixing all these issues?

Thanks

Hey @sanctibrouwer,

My apologies; I forgot to update your thread.
Yes, version 6.0 resolved the conflict with WooCommerce Bookings that was originally reported. We received lots of positive feedback, so you should be safe to update.
However, we are still working on a final solution to prevent dependency conflicts like this. We can not guarantee that it might not happen again when another plugin updates its dependencies until we have a solution.
But it is one of our top priorities, so please let us know if you experience any similar issues again.

Kind regards,
Niklas