Title: Fatel Error Activating Plugin
Last modified: May 22, 2023

---

# Fatel Error Activating Plugin

 *  Resolved [yoibe1](https://wordpress.org/support/users/yoibe1/)
 * (@yoibe1)
 * [3 years ago](https://wordpress.org/support/topic/fatel-error-activating-plugin/)
 * I am getting this error every time I try to activate the plugin:
 * ![](https://i0.wp.com/cvrgeny.com/Screenshot%202023-05-22%20at%2011.10.52%20AM.
   png)
 * Any ideas what’s causing it?

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

 *  Plugin Support [Syde Joost](https://wordpress.org/support/users/joostvandevijver/)
 * (@joostvandevijver)
 * [3 years ago](https://wordpress.org/support/topic/fatel-error-activating-plugin/#post-16759778)
 * Hello [@yoibe1](https://wordpress.org/support/users/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](https://wordpress.org/themes/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](https://woocommerce.com/document/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
 *  [Room 34 Creative Services, LLC](https://wordpress.org/support/users/room34/)
 * (@room34)
 * [3 years ago](https://wordpress.org/support/topic/fatel-error-activating-plugin/#post-16771512)
 * 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](https://stackoverflow.com/a/70252458)
   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.
    -  This reply was modified 3 years ago by [Room 34 Creative Services, LLC](https://wordpress.org/support/users/room34/).
 *  Plugin Support [Syde Joost](https://wordpress.org/support/users/joostvandevijver/)
 * (@joostvandevijver)
 * [3 years ago](https://wordpress.org/support/topic/fatel-error-activating-plugin/#post-16775950)
 * Hello [@yoibe1](https://wordpress.org/support/users/yoibe1/) and [@room34](https://wordpress.org/support/users/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](https://paypal.inpsyde.com/docs/request-support/).
 * Let me know if you agree with this statement or if you believe another course
   of action should be taken.
 * Kind regards,
   Joost
 *  Plugin Support [Syde Joost](https://wordpress.org/support/users/joostvandevijver/)
 * (@joostvandevijver)
 * [3 years ago](https://wordpress.org/support/topic/fatel-error-activating-plugin/#post-16793476)
 * 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

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

The topic ‘Fatel Error Activating Plugin’ is closed to new replies.

 * ![](https://ps.w.org/zettle-pos-integration/assets/icon-256x256.png?rev=2694076)
 * [PayPal Zettle POS for WooCommerce](https://wordpress.org/plugins/zettle-pos-integration/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/zettle-pos-integration/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/zettle-pos-integration/)
 * [Active Topics](https://wordpress.org/support/plugin/zettle-pos-integration/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/zettle-pos-integration/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/zettle-pos-integration/reviews/)

 * 4 replies
 * 3 participants
 * Last reply from: [Syde Joost](https://wordpress.org/support/users/joostvandevijver/)
 * Last activity: [3 years ago](https://wordpress.org/support/topic/fatel-error-activating-plugin/#post-16793476)
 * Status: resolved