WP Deactivated a Plugin…..but which one?

  • Resolved kalico

    (@kalico)


    9 years ago

    I just got a message in history that says “WordPress: Deactivated a plugin because of an error: Plugin file does not exist.”

    That’s all well and good, but I was nowhere near the plugin page when this happened. In fact, I was on the dashboard looking at the history, when it refreshed and showed me that message.

    So how would WP just “suddenly” decide to deactivate a plugin?

    We did have a spate of fake logins just a short while ago, that brought down the MySQL server. That’s why I was looking at the history, and seeing the 386 fake login attempts. So I’m a little suspicious of everything right now.

    If this is legit, it would be a great improvement if the output from Simple History could tell exactly which plugin was deactivated and/or which file was not found.

    Any thoughts?

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Pär Thernström

    (@eskapism)

    9 years ago

    There is only a few places in WordPress where that message could come from. Most common is when an admin visits the plugin page, because then WordPress is validating all active plugins to see that they are all ok (and that their files still exist). But the message could also come from plugins like Jetpack that can manage plugin updates.

    If you click the date/time of the event you can get some more info about the event and maybe something there can give you a clue on what happened.

    Finally, yes it would be great if Simple History also logged the name of the plugin that was disabled due some problem. I’ve taken another look at this now and I think I have a solution for the next version of the plugin!

    Thread Starter kalico

    (@kalico)

    9 years ago

    @eskapism Thanks for the reply. I don’t have Jetpack, and don’t know of anything running on cron like that, but I’ll look into it. The only clue in the “date/time” modal is that the referer was http://mysite.com/wp-admin. Doesn’t mean much to me, except that it wasn’t the plugins.php page itself. 🙂

    I’m glad you have a possible solution for exposing the source. That would be a great enhancement.

    WordPress is similarly silent when it deactivates or activates a plugin. It just says “Plugin (de)activated” and I sometimes think — wait, which one did I click on? 🙂

    Thanks again for the quick response.

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

The topic ‘WP Deactivated a Plugin…..but which one?’ is closed to new replies.

  • 2 replies
  • 2 participants
  • Last reply from: kalico
  • Last activity: 9 years ago
  • Status: resolved