Plugin could not be activated because it triggered a fatal error.

  • I have tried installing it on multiple fresh installs of wordpress using different databases and every time I try to activate one of the plugin that comes with my theme called “Booked”, I get the following error.

    “It looks like something went wrong when trying to fetch data from the Font Awesome API:”

    So I figured, ok, I’ll try to install the plugin Font Awesome. I can install it but I can never successfully activate it. I get the following error.

    “Plugin could not be activated because it triggered a fatal error.”

    I also tried Better Font Awesome and when I activate that one, it says it’s not really active

    “It looks like something went wrong when trying to fetch data from the Font Awesome API:

    :

    Don’t worry! Better Font Awesome will still render using the included fallback version:?5.14.0. This may be the result of a temporary server or connectivity issue which will resolve shortly. However if the problem persists please file a support ticket on the?plugin forum, citing the errors listed above.”

    But that makes my wordpress backend really slow, like 14seconds slow per click.
    Oh yeah, the support team from my hosting company Whc.ca tried to install it on another server of theirs and it did not work either.

    So I decided to rent another webhost and I’m able to install the plugin without any issues.

    Any ideas why my other host does not let me activate the plugin?

Viewing 1 replies (of 1 total)
  • Plugin Author mlwilkerson

    (@mlwilkerson)

    @modepc It sounds like this might be related to Web Application Firewall rules. If so, then it would make sense that using a different hosting provider has different results, because those security rules would be something set by the hosting environment.

    I’ve just released plugin version 4.5.0 which changes how requests to the WordPress REST API are made, so that it better accommodates typical Web Application Firewall configurations. You might give it a shot.

    However, depending on the “Booked” plugin integrations with ours (I don’t know) it may or may not automatically use a newer version of our plugin when available. But you could give it a shot.

    1. install and activate the latest version of our plugin
    2. try your scenario again and see if it works
Viewing 1 replies (of 1 total)
  • You must be logged in to reply to this topic.