• Resolved coldrealms65

    (@coldrealms65)


    No matter what plugin it is trying I get this error:
    “When enabling the plugin, “name of plugin I am trying”, a site failure occurred. Because of this the change was automatically reverted. ”

    It does not matter what is being activated or what state the site is in, if troubleshooting is on this error happens.

    Seems the check is broken

    Also, can we get an option to activate troubleshooting mode without disabling any plugins so we can test removing one at a time?

Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter coldrealms65

    (@coldrealms65)

    This also happens on Theme switching – FYI

    Plugin Author Marius L. J.

    (@clorith)

    Hiya,

    Just a quick check, if you go to Tools > Site Health, does it report any issues with Loopbacks?

    As for starting with everything enabled, that is technically possible already, in the plugin list, you can select all, and the bulk action menu will allow you to choose to start troubleshooting with the chosen plugins active (we are looking into different ways of entering this mode in the future as well though).

    Thread Starter coldrealms65

    (@coldrealms65)

    Thanks for getting back to me.
    No, site health is good. No errors of any kind.

    I had no idea yous could start troubleshooting that way. Thanks for the tip!

    Same thing happened to me. No warnings except to delete unused plugins.

    This same thing just happened to me, I got the same error “When enabling the plugin -name of plugin- a site failure occurred…”
    I see people having this issue for a few weeks now.

    The way I was able to do it was to force enable the Health and Troubleshoot plugin, after this one was enabled then I was able to enable the others without any errors.

    Plugin Author Marius L. J.

    (@clorith)

    Hiya,

    This was caused by a bug in the validation process when enabling/disabling a plugin or theme during troubleshooting mode. Although using the new “force enable/disable” feature would allow you to bypass this, it was obviously not a great user experience.

    Version 1.5.1 which just rolled out is a maintenance release that addresses this specific issue, hopefully it’ll work out better for your going forward ??

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Every plugin triggers an error’ is closed to new replies.