Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author David Anderson / Team Updraft

    (@davidanderson)

    None known yet… what is the text of the error message?

    David

    Plugin Author David Anderson / Team Updraft

    (@davidanderson)

    P.S. To see the text of the message, scroll the box in which WordPress says that there was a fatal error.

    David

    Thread Starter John

    (@johnmcole)

    Hi David,

    Thanks for the help. No specific error message, it just says:

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

    Nothing in the PHP error logs either.

    John

    Plugin Author David Anderson / Team Updraft

    (@davidanderson)

    Strange. Do you get a message if you turn WP_DEBUG in wp-config.php to true?

    Failing that, you could try selectively de-activating other plugins, to see if that then reveals a clash with one in particular. (It’ll probably activate if you de-activate WooCommerce, but that’s a red-herring – if WooCommerce is not active, then it deliberately puts itself into an inactive mode).

    David

    Thread Starter John

    (@johnmcole)

    David,

    I tried going through all of the plugins and selectively deactivated and reactivated them to see if I could narrow it down to a plugin conflict – but the only one that made a difference was WooCommerce which is a red-herring as you said.

    I just switched to Twenty Thirteen to rule out a theme issue, deactivated all plugins except for WC and WooCommerce EU VAT Compliance (Free) v1.6.8 and still got the fatal error upon activation.

    I turned on debug mode and I’m not seeing anything helpful.

    This is really weird.

    John

    Plugin Author David Anderson / Team Updraft

    (@davidanderson)

    Hi John,

    Weird indeed!

    I think if you de-activate WooCommerce, then activate WooCommerce EU VAT Compliance, and then activate WooCommerce, then it’s possible that you’ll then be able to read an error message – especially if you set WP_DEBUG in your wp-config.php to true. Possibly, though, it’ll instead refuse to activate WooCommerce instead. In that case, you could force-activate it by editing the ‘active_plugins’ option in your options table, if you’re confident enough to edit serialized strings – then, with WP_DEBUG on, you should get to see what the fatal error actually is by visiting the front page. (But make sure you edit the serialized string correctly – otherwise it’ll effectively have no plugin activated).

    David

    Plugin Author David Anderson / Team Updraft

    (@davidanderson)

    Hi John,

    I think I’ve solved this, in the just-released version 1.6.11.

    There was a fatal error on PHP 5.2, which is now resolved. So, I assume you had that. Please try again now!

    Best wishes,
    David

    Thread Starter John

    (@johnmcole)

    Hi David,

    Thanks for that. It looks like the latest plugin update fixed the issue!

    Best,
    John

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

The topic ‘Fatal error with version 1.6.7 on plugin activation’ is closed to new replies.