• craven222

    (@craven222)


    I just switched themes and I’m getting this error on every plugin I try to active (no additional details – error reporting is on full – I tried checking /var/log/php.log but it hasn’t been updated since Oct 2013)

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

    Also happens on new plugins I install & try to activate.

    Going to update to 3.9 to see if that fixes anyway.

    Any help appreciated

    Ta

Viewing 15 replies - 1 through 15 (of 21 total)
  • EMG

    (@emg)

    Hi there! 🙂

    1) Does swapping to a different theme clear the problem?

    2) Is your hosting’s PHP up to date?

    I ask this because I have heard of some cases where the web host’s PHP is out of date and so the plugin is not supported.

    3) Are the plugins compatible with your version of WordPress?

    Though some plugins can still work if there is a version mismatch, other times they can cause errors including ‘fatal’ ones.

    Thread Starter craven222

    (@craven222)

    Thanks for the response.

    1) Yes, as this only started happening when I activated a new theme

    2) Yep, version info is 5.5.5.1

    3) This is happening across the board, with every plugin.

    EMG

    (@emg)

    Hello again! 🙂

    Thanks for reporting back with the information.

    From what you’re reporting it sounds like, then, that the problem is possibly somehow theme-specific.

    If switching to ANY theme triggers this problem, then maybe not so, but if this theme in particular is triggering it and no other themes, then we can be almost assured that the theme itself is causing a problem.

    Unfortunately, this might mean that you won’t be able to use the theme without further support from the theme author.

    Before we say this, however, let’s check one last thing.

    Deactivate all of your plugins (or, if you don’t mind, deleting them), reload your Admin dashboard, and reactivate the plugins (if you deleted, reinstall and reactivate).

    WordPress did recently upgrade to 3.9 (did you also upgrade WordPress?) and it’s possible that sometimes during upgrades, compatibility errors are temporarily triggered which can be cleared out by a simple deactivate and reactivate (or uninstall, reinstall).

    Thread Starter craven222

    (@craven222)

    I’m using this theme:

    http://wordpress.org/themes/twentyfourteen

    >If switching to ANY theme triggers this problem, then maybe not so, but if this theme in particular is triggering it and no other themes, then we can be almost assured that the theme itself is causing a problem.

    The only other themes I have installed is the default (twenty twelve) and it’s producing the same error.

    >Deactivate all of your plugins (or, if you don’t mind, deleting them), reload your Admin dashboard, and reactivate the plugins (if you deleted, reinstall and reactivate).

    They’re already deactivated – I can’t activate any of them. Tried installing a new plugin and I get the same error

    >WordPress did recently upgrade to 3.9 (did you also upgrade WordPress?) and it’s possible that sometimes during upgrades, compatibility errors are temporarily triggered which can be cleared out by a simple deactivate and reactivate (or uninstall, reinstall).

    I’m still on 3.8. I might try and update to 3.9 to see if that solves it?

    EMG

    (@emg)

    You can go ahead and try and upgrade though I would definitely suggest making a backup first.

    I’m racking my brain here trying to figure out what other scenario might trigger such a thing as normally, a simple theme switch ought not trigger something like this happening.

    Going to do some more research and see what I can come up with and if I can’t figure anything else out, I’ll see if I can tag someone else to come look at this.

    If it’s nothing you yourself did and if WordPress hasn’t updated on its own, I’m wondering if your host updated/changed something on their end.

    Edit 1: Also, can you paste a copy of the exact error message you’re seeing please?

    Edit 2: If you can FTP into your site, and you don’t mind doing this, I would recommend deleting the plugins altogether and seeing if that clears your problem. And then, try reinstalling one by one.

    I’ve been doing some looking around and it seems like that is one way to clear the problem. If you search the forum using the title of your post, you’ll see what I mean.

    Somehow, a plugin – even deactivated – can still somehow cause problems like the one you’re having now and in those cases, deleting the plugin completely and trying again or simply deleting (because somehow, it’s broken) clears out the problem.

    Thread Starter craven222

    (@craven222)

    Thanks for the help EMG. I will probably try the upgrade on the off-chance that it fixes it.

    The message I’ve posted in the topic is the entire message, I have root control over my VPS so there isn’t anyone else with access to change anything.

    EMG

    (@emg)

    You’re welcome! I’m just sorry I can’t be of more help.

    If you haven’t already, try turning on Debug mode in WordPress and see if you generate a more specific error besides the Fatal Error.

    Debugging in WordPress

    This might help provide a clearer view on what, exactly, is causing the problem.

    Thread Starter craven222

    (@craven222)

    This is the theme I’m using for anyone else finding this topic

    http://wordpress.org/themes/twentyfourteen

    EMG

    (@emg)

    Have you tried the Debug mode yet to see if we can generate a more specific error message?

    Thread Starter craven222

    (@craven222)

    Yep, I have

    define(‘WP_DEBUG’, true);
    define(‘WP_DEBUG_LOG’, true);
    define(‘WP_DEBUG_DISPLAY’, false);
    @ini_set(‘display_errors’, 0);

    in my wp-config.php – but it’s not giving me any errors. I’ll be looking through my PHP logs if this wordpress update doesn’t fix anything.

    EMG

    (@emg)

    Thanks for confirming; I just realized after asking you mentioned it in your OP (sorry for missing it!).

    I’m going to see if I can tag someone for you. 🙂

    Moderator Jan Dembowski

    (@jdembowski)

    Forum Moderator and Brute Squad

    I tried checking /var/log/php.log but it hasn’t been updated since Oct 2013)

    Check with your web hosting but that’s probably not the right error log.

    Can you provide a link to your site? If you don’t want to that’s fine but a link often let’s others see something you may have missed.

    Apologies if you’ve posted it already and I missed it.

    Thread Starter craven222

    (@craven222)

    Moderator Jan Dembowski

    (@jdembowski)

    Forum Moderator and Brute Squad

    Looks like you may have an incomplete upgrade to 3.9.

    This link shows 3.9

    http://ablemagazine.co.uk/readme.html

    But the source for this page includes references to 3.8.1

    http://ablemagazine.co.uk/stories/column-tom-wentworth/

    <link rel='stylesheet' id='twentyfourteen-style-css'  href='http://ablemagazine.co.uk/wp-content/themes/twentyfourteen/style.css?ver=3.8.1' type='text/css' media='all' />

    It’s the ver=3.8.1 part of that HTML line.

    Please try these steps:

    1 – Make a full backup of your site files and database.

    http://codex.wordpress.org/WordPress_Backups
    http://codex.wordpress.org/Backing_Up_Your_Database
    http://codex.wordpress.org/Restoring_Your_Database_From_Backup

    Backups are your friend and a great safety net in case anything else goes wrong. Better safe than sorry.

    2 – Try the manual update steps after that backup is safely made and stored off of your web server.

    http://codex.wordpress.org/Updating_WordPress#Manual_Update

    All of the WordPress files have to be updated and having an installation that’s not fully updated can cause problems.

    Please make sure you don’t delete wp-config.php or wp-content and give that update link a good read.

    Thread Starter craven222

    (@craven222)

    Yeah that’s a non-related issue. I updated to 3.9 to fix the issues but some of the files must’ve not uploaded properly. Trying again now.

Viewing 15 replies - 1 through 15 (of 21 total)
  • The topic ‘Plugin could not be activated because it triggered a fatal error.’ is closed to new replies.