Since November 29 I keep finding a few of my WordPress sites with all of their plugins disabled (except for one called "Manage WP - Worker"). Each time this happens, it seems that there's an error at the top of the plugins page in WordPress that says:

The plugin 1 has been deactivated due to an error: Plugin file does not exist.

I've done some searches in Google to see if anyone else has experienced this, but so far I've only seen that people are showing a different error; one that actually contains a plugin name/php file instead of the number 1, like in my error.

When I find all plugins deactivated I can simply activate them again, and then it seems that the sites will be running fine for several days. Then the problem reoccurs.

What could cause this? Could it be orphaned tables in the WordPress database? I can, by the way, with nearly 100% certainty say that my site hasn't been hacked; I've got an awesome security plugin called BulletProof Security Pro and also checked out my site with Sucuri's free security/malware checker and no malware was found.

I've contacted my hosting provider, the company that makes the "Manage WP - Worker" since theirs is the only one that ever stays activated, and also BulletProof Security Pro, but the responses I've gotten from each is that: 1) I or another webmaster is manually deactivating plugins 2) I or another webmaster are deactivating the plugins via the database somehow 3) There's a hack

I can rule out each one of these three. So, I'm reaching out here to see if anyone has any ideas about what's happening.

Thank you!

  • I can't comment because I don't have 50 reputation. So... Did GoDaddy resolve the plugin issue for you? I have exactly the same issue on one of my sites (also using ManageWP, which also stays activated). Is there a later version of the plugin I can access? Thanks, Gregor Feb 25, 2017 at 9:12
  • Hi, I'm not sure if GoDaddy actually did anything. I did notice a couple more updates to the object-cache.php file and I haven't seen the same issue reoccur. Mar 24, 2017 at 20:38

1 Answer 1


@Jutta, this is a hard question to answer. Many unknowns. What you may do is to understand the error. WordPress may have the error log. Set define( 'WP_DEBUG_LOG', true ); in your config file, and then you need to check the results as per this article.

Note that this allows you to write to /wp-content/debug.log

A web server may have the error log. Work with your Hosting support if WordPress error log cannot help. This is not strictly WordPress item, so I will be a fish in there.

You can work on both these to understand your problem better. Please update your question with more details once you find that.

You may even consider accepting my answer if you like it, or if you think it is helpful, because this is a general approach what to do. We may create additional questions for specific errors we may find on your web server.

  • Thank you so much @prosti. I've enabled the debug mode. The article you provided was very helpful. I'm just wondering how soon after enabling this in the wp-config.php file I should expect to see anything in the debug.log file? Also, will enabling this debug mode create its own debug.log file, or do I need to make one? Jan 2, 2017 at 18:59
  • I expect the very next time you get the The plugin 1 has been deactivated due to an error: Plugin file does not exist. we may catch something in the debug.log
    – prosti
    Jan 12, 2017 at 2:52
  • Thanks! It actually turned out the be a bug in the object-chache.php file which comes with the GoDaddy Managed WordPress hosting environment. That file acts like a plugin.... I think that's why I would see that odd error message. Appreciate your help! Jan 31, 2017 at 18:54
  • Oh, this is interesting. Nice feedback. Glad you sorted this out @JuttaDuncan.
    – prosti
    Jan 31, 2017 at 19:03

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.