• Resolved enollo

    (@enollo)


    I forgot to deactivate the Dashboard plugin before updating to the latest beta. Everything was fine until I logged out and tried to log back in (which finally brought me to the Dashboard, but showed a fatal error instead)

    I suspect most people that are using MP6 and/or Dashboard are pretty comfortable manually disabling a plugin in this case, but it might be a good idea to foolproof it as these plugins are getting pretty popular.

    I’m not sure which way to approach the conflict resolution. Maybe check to see if the plugins are active and force them to deactivate, displaying an alert notifying the user of the actions taken.

    Thanks for listening ??

Viewing 3 replies - 1 through 3 (of 3 total)
  • Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    A force deactivate might be better, since sometimes the ‘break’ might stop you from being able to get into WP…. That’s tricky.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    Okay, I opened https://core.trac.www.ads-software.com/ticket/26334 because … yeah. This needs it.

    Thread Starter enollo

    (@enollo)

    Thanks ??
    Just like you stated in the ticket, I was also concerned about the less techy people. Especially if WordPress continues developing features as plugins first (which is a great way to go), people with all sorts of backgrounds will stumble upon these plugins and they may not know what to do when an official release comes around. Automatic updates make it even harder to pinpoint the issue.

    I agree, the plugins should be forced to deactivate on WP core update. I think the user shouldn’t be allowed to active it again, and an alert similar to the “update available” alert should inform the user that the plugin can be safely deleted.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘WrodPress 3.8 Beta – Suggestion to check for activated feature plugins’ is closed to new replies.