Hello @yoibe1
Thank you for reaching out to us, we are here to help.
This type of error sometimes occurs when 2 plugins are using similar resources. You may want to perform a full conflict test to confirm this and to possibly isolate what plugin/theme is causing this. We recommend temporarily activating the default theme Storefront and disabling all other plugins except for WooCommerce and PayPal Payments to see if the behavior persists. Here’s a guide that explains the steps in more detail: How to test for conflicts.
Once you know what plugin is causing this and we can reproduce it, our developers could take a look is there is anything they can do to correct this.
Please let me know how this goes and if you require addititional support.
Kind regards,
Joost
I just had a client’s site blow up because of this issue. I tracked down about a dozen instances of has() methods in various files throughout the plugin that were throwing this fatal error. The solution is to append : bool between has() and the { in each instance. I don’t do a lot of development that relies on dependencies like this so it’s not something I’m super familiar with, but this StackOverflow post helped me sort it out.
Unfortunately this did mean I had to hack the Zettle plugin to make these changes throughout. I suppose it’s possible there’s a plugin conflict, but it looks to me more like a straightforward issue of the Zettle plugin not adhering to the requirements of one of its dependencies. This kind of thing is why I’m wary of this kind of “house of cards” development approach, although I know my old school way has its own limitations.
Hello @yoibe1 and @room34
We have not heard of this issue more often, so we are fairly sure this is caused by a plugin conflict. We also always advise to first test our (or any other) plugin first on a staging site to make sure this type of situation does not take down your website and cause your business harm.
If we are to look further into this situation, we would need to get more information and also the outcome of your conflict tests that were performed. If you believe this is something that is caused by our plugin and can be avoided, we need to be able to reproduce the issue on our own testing environment. For this, it would be best to open a private engagement, so we can easier exchange details on your website and the settings they have. You can open such a private engagement following these instructions.
Let me know if you agree with this statement or if you believe another course of action should be taken.
Kind regards,
Joost
Hello,
since we did not receive any response or follow-up questions from you, we will assume you got this working to your requirements. If you still have any more questions for us, please open a new thread, because we will mark this one as resolved.
Kind regards,
Joost
