Debugging & Profiling

A Plugin Deactivated Itself: Find Out Why, Get Alerted

A plugin deactivated itself? Five causes with a check for each, which activity log plugins catch it, and two scripts that alert you next time.

Varun DubeyVarun Dubey
·15 min read
Plugins screen with one add-on plugin switched off and a question mark badge, showing a plugin that deactivated itself

A plugin deactivates itself for one of five reasons: WordPress could not find its main file, an update was interrupted, something other than you changed the setting (the host, another plugin, a script or an attacker), the stored plugin list was overwritten, or the plugin is not deactivated at all and is paused after a fatal error. Start by checking whether the plugin folder still exists and when its files last changed. That one check separates the causes faster than anything else.

WordPress core keeps no record of who or what switched a plugin off, so you work it out from evidence. This guide shows the check for each cause, which logging plugins would have caught it, and two small pieces of code that tell you within minutes the next time it happens.

Everything we say about core behaviour below comes from the WordPress 7.1.4 source (the current release on 15 Nov 2026), with the file named so you can read it yourself. Commands are read-only unless marked “Changes the site”. We checked the code samples on 15 Nov 2026 with a PHP syntax check and a stub test of the diff logic. We have not run the must-use plugin on a production site, so try it on staging first.

First: is the plugin deactivated, paused or missing?

These three look identical from the front of the site and have different causes. Run these before anything else.

# Checked on 15 Nov 2026 (WP-CLI 2.12)
# What WordPress has stored as active
wp option get active_plugins --format=json

# Status, version and pending update for every plugin
wp plugin list --fields=name,status,version,update

# Is the folder on disk, and when did its files last change?
ls -la wp-content/plugins/ | grep -i 'YOUR-PLUGIN'
stat -c '%y %n' wp-content/plugins/YOUR-PLUGIN/*.php 2>/dev/null | sort | tail -3

What you see

What it usually means

Go to

Folder missing or nearly empty

The files were removed, and WordPress later dropped the plugin from the active list.

Cause 1

Folder present, files dated at the incident, status inactive

An update replaced the files and the plugin did not come back on.

Cause 2

Folder present, files old, status inactive

The setting changed without touching the files.

Causes 3 and 4

Listed as active, features not running, crash or “technical difficulties” page

A fatal error. Recovery mode may have paused it.

Cause 5

Inactive on one multisite site only

Site-level and network-level lists are stored separately.

Multisite note below

On multisite, a plugin can be active for one site or for the whole network, and the two lists live in different places:

wp site option get active_sitewide_plugins --format=json
wp option get active_plugins --format=json --url=https://the-affected-site.example

What does “Plugin file does not exist” mean?

It means WordPress looked for the plugin’s main file, did not find it, and removed the plugin from the active list. The full notice reads “The plugin X has been deactivated due to an error: Plugin file does not exist.” The files were deleted, moved or never fully copied, so the fix is to reinstall them.

How it works. On every load, WordPress builds its list of plugins to include with wp_get_active_and_valid_plugins() in wp-includes/load.php. That function only skips a plugin whose file is missing. It does not change the stored list. The actual deactivation happens later, when someone opens wp-admin/plugins.php: that screen calls validate_active_plugins() (wp-admin/includes/plugin.php), which runs deactivate_plugins( $plugin, true ) for each plugin that fails validation. The true is the silent flag.

Two consequences follow. The deactivation is stamped when an admin looked at the Plugins screen, which can be hours or days after the files vanished. And because it is silent, the usual deactivation hooks do not fire. Until that screen is opened, wp plugin is-active still reports the plugin as listed, with a warning that the plugin no longer exists.

Why files go missing:

  • A failed update. WordPress removes the old folder before copying the new one in, so a full disk, timeout or permissions error can leave it empty.
  • A deployment or sync that treats the server’s plugin folder as disposable and did not include this plugin.
  • A host restore of files to a date before the plugin was installed.
  • A malware scanner or host scan that removed or quarantined a file.
  • Someone deleting the folder over SFTP.
# Checked on 15 Nov 2026
# Leftovers from an interrupted update
ls -la wp-content/upgrade/ wp-content/upgrade-temp-backup/ 2>/dev/null
ls -la .maintenance 2>/dev/null

# Disk space, and is the plugins folder writable by the PHP user?
df -h .
ls -ld wp-content/plugins

# Quarantine folders scanners commonly create
find wp-content -maxdepth 2 \( -iname '*quarantine*' -o -iname '*infected*' \) 2>/dev/null

A plugin folder inside wp-content/upgrade-temp-backup/plugins/ is the copy WordPress keeps so it can roll an update back. If it is there, an update started and did not finish cleanly. A leftover .maintenance file says the same.

Fix. Reinstall the plugin at the version you were running, then activate it. Settings sit in the database and are normally untouched.

# Changes the site. Checked on 15 Nov 2026: --version, --force and --activate are documented flags.
wp plugin install YOUR-PLUGIN --version=X.Y.Z --force --activate
# For a commercial plugin, pass the path to the vendor's zip instead of the slug.

Can an update deactivate a plugin if auto-updates are off?

Yes, but only on one specific path. When a single active plugin is updated through the old non-JavaScript route (wp-admin/update.php?action=upgrade-plugin), WordPress switches it off first and relies on a follow-up request to switch it back on. If that follow-up never completes, the plugin stays off.

What the source says. Plugin_Upgrader::upgrade() adds the filter deactivate_plugin_before_upgrade(), whose comment reads “Deactivate the plugin silently, Prevent deactivation hooks from running.” After the new files are in, Plugin_Upgrader_Skin::after() loads an iframe pointing at update.php?action=activate-plugin. That page prints “Plugin reactivated successfully,” or “Plugin failed to reactivate due to a fatal error.” A closed tab, a timeout, a proxy cutting the connection or a fatal error in the new version all leave the plugin inactive.

The normal “Update now” button in the dashboard works differently. It calls wp_ajax_update_plugin(), which uses bulk_upgrade(), and in the 7.1.4 source that path does not add the deactivate filter. So an inactive plugin after a routine dashboard update points to something else, usually a fatal error or a missing-file cleanup.

Background auto-updates take a third path. deactivate_plugin_before_upgrade() returns early when wp_doing_cron() is true, with the comment “don’t deactivate the plugin, as we require a browser to reactivate it.” Instead, WP_Automatic_Updater puts the site in maintenance mode, updates, makes a loopback request to look for a fatal error, and if it finds one it restores the previous version from upgrade-temp-backup and records either “The previously installed version has been restored” or “could not be restored.” So turning auto-updates off does not remove the risk. It removes the path that has a built-in rollback.

Third-party updaters are the other candidate. MainWP’s own documentation says it triggers the update but WordPress on the child site performs it, and that a failed run can leave the folder incomplete or missing so WordPress treats the plugin as uninstalled or deactivates it. It lists server memory and time limits, security or caching plugin conflicts, a firewall blocking the download and file permission problems as typical causes (checked 15 Nov 2026).

How to check. Look for update requests in the access log around the time the files changed.

# Checked on 15 Nov 2026. Adjust LOG for your host.
LOG='/var/log/nginx/access.log*'

# Update and reactivation requests
zgrep -hE 'update\.php\?action=(upgrade-plugin|activate-plugin|update-selected)|admin-ajax\.php.*update-plugin' $LOG | tail -40

# Explicit deactivation clicks, single and bulk
zgrep -hE 'plugins\.php\?action=deactivate|plugins\.php.*deactivate-selected' $LOG | tail -20

You are looking for an upgrade-plugin request with no activate-plugin request after it, or one that returned a 5xx or ran to the timeout. Then read the PHP error log for the same minute:

grep -nE 'Maximum execution time|Allowed memory size|PHP Fatal' /path/to/php-error.log | tail -20
tail -100 wp-content/debug.log 2>/dev/null

Management tools and host panels update through their own connectors, so their requests will not match the lines above. Check that tool’s history for the site and time, and ask the host whether a job ran.

Fix and prevent. Activate the plugin and load the pages that depend on it. To stop a repeat, update from the command line or a tool that does not need a browser tab open, test on a copy first, and keep a rollback. Our update policy guide covers the order and the checks.

# Changes the site.
wp plugin activate YOUR-PLUGIN
wp plugin get YOUR-PLUGIN --fields=name,status,version

Can the host, another plugin or a script deactivate it?

Yes, and with the files untouched and an old modified date, this is the next place to look. There are four candidates.

  • A person or script. The access-log lines above show dashboard clicks with IP and time. For WP-CLI or deployment scripts, search the site user’s shell history and your deploy scripts for wp plugin deactivate.
  • The host. WP Engine’s support page on disallowed plugins says that if you have one of the listed plugins “you’ll be notified and the plugin will eventually be removed from your site” (page dated 28 Jul 2025, read 15 Nov 2026). A removed plugin then becomes a Cause 1 case the next time an admin opens the Plugins screen. Other hosts keep their own lists, and managed hosts often enforce them with must-use plugins. Check your host’s list and its activity log.
  • Another plugin. Security, staging, migration and “health check” plugins can switch plugins off, and a troubleshooting mode left on is a common one. A plugin can also deactivate itself when something it needs is missing: an add-on that cannot find its parent, or finds it too old, may call deactivate_plugins() on its own file.
  • An attacker. Switching off a security plugin is a routine early step. If the plugin that went off is a firewall or scanner, jump to the compromise section below.

To find which installed code can deactivate plugins:

# Checked on 15 Nov 2026
grep -rn --include='*.php' 'deactivate_plugins\s*(' wp-content/plugins wp-content/mu-plugins wp-content/themes \
  | grep -v '/node_modules/' | head -40

Most hits will be a plugin deactivating itself when its own requirements fail, which is normal. Read the condition around each hit. If the plugin that went off appears with a version or dependency check beside it, compare that requirement with what is installed. A parent updated ahead of its add-on, or the reverse, can trip exactly this. WordPress 6.5 added a core Plugin Dependencies feature, and the help text on the Plugins screen says an add-on’s activate button is disabled until its required plugins are active, so check the “Requires Plugins” header of the add-on too. For a wider look at what a PHP bump breaks, see our PHP upgrade check.

Could the stored plugin list have been overwritten?

Yes. The active list is one row in the options table, named active_plugins. Anything that replaces that row with an older or different copy changes which plugins run, with no deactivation event at all.

  • A database restore or a staging-to-live push. If staging had the plugin off, pushing its database turns it off on live. Compare the dates of your last restore or push with the incident.
  • A persistent object cache serving a stale copy. With Redis or Memcached, autoloaded options are cached together. Two requests saving options at nearly the same moment can leave the cache holding an older copy of that group, including an older plugin list, and a later write can save that stale list back.
  • A search-and-replace or migration tool that damaged the serialized value. In validate_active_plugins(), a value that is not an array is replaced with an empty array, so every plugin goes off at once.
# Checked on 15 Nov 2026
# What the database holds, against what WordPress reads (possibly from cache)
wp db query "SELECT option_value FROM $(wp db prefix)options WHERE option_name='active_plugins'" --skip-column-names
wp option get active_plugins --format=json

# Is a persistent object cache in use?
wp cache type
ls -la wp-content/object-cache.php 2>/dev/null

If the two outputs list different plugins, the cache is stale. If every plugin went off together, suspect a damaged value or a restore.

# Changes the site: clears the object cache.
wp cache flush

Did recovery mode pause it after a fatal error?

If the plugin shows as active but its features are gone, a fatal error is the likely reason. Since WordPress 5.2, core catches fatal errors, emails the site admin, and offers a recovery mode session in which the failing plugin is paused. A paused plugin is skipped on load but stays in the active list, so the Plugins screen still calls it active.

The detail people miss. Reading wp-includes/class-wp-recovery-mode.php, handle_error() sends the email only when the fatal error happens on a protected endpoint: the admin, the login page, or a protected Ajax action (is_protected_endpoint() in wp-includes/load.php). A fatal error on a public page sends nothing. The email is rate limited to one per day by default (filter recovery_mode_email_rate_limit). It goes to the address in the RECOVERY_MODE_EMAIL constant if defined and valid, otherwise to the site’s admin_email. The subject is “[Site name] Your Site is Experiencing a Technical Issue.”

Pausing happens only inside a recovery session. The link in the email starts one, with a cookie lasting a week by default (filter recovery_mode_cookie_length). While the session is active, paused plugins are stored in an option named {session_id}_paused_extensions. Leaving recovery mode deletes those options. So running wp option list --search='*_paused_extensions' from the server shows something only while a session exists. If nobody clicked the email link, the plugin is not paused: visitors simply get the error page while the plugin remains active in the list.

The site owner can turn all this off. Setting WP_DISABLE_FATAL_ERROR_HANDLER to true, or filtering wp_fatal_error_handler_enabled, disables the handler, and then there is no email and no pause.

# Checked on 15 Nov 2026
wp option list --search='*_paused_extensions' --format=table
grep -n 'PHP Fatal' /path/to/php-error.log | tail -20

Search the inbox of the admin address for “Your Site is Experiencing a Technical Issue.” On many sites that address belongs to someone who left years ago, which is why nobody saw it. The email names the plugin and the error.

Fix. Read the fatal error and fix its cause. Typical triggers are a PHP version change, or a plugin updated ahead of the one it depends on. Then use the Resume action on the Plugins screen in recovery mode.

Why are there no log entries?

Because core keeps no activity log, and the hook most logging plugins listen to does not fire in the cases that matter here.

That hook is deactivated_plugin. Inside deactivate_plugins() it sits behind if ( ! $silent ), and core’s own comment says: “If a plugin is silently deactivated (such as during an update), this hook does not fire.” The missing-file cleanup and the non-JavaScript update path both use the silent form. A restored database value never calls the function at all.

The silent form still ends with update_option( 'active_plugins', $current ). So the option itself is the one door every route passes through, except a direct database write. A logger that watches only deactivated_plugin will say nothing happened. One that also watches the option will not.

Which activity log plugins would have caught it?

We downloaded the current release of each plugin from WordPress.org on 15 Nov 2026 and searched the source for the hooks it registers for plugin changes. Store numbers come from the WordPress.org plugin API on the same day.

Plugin (version)

Listing on 15 Nov 2026

Plugin hooks we found

Silent deactivations

WP Activity Log 5.7.0

94/100 from 492 ratings, 300,000+ installs, updated 5 Nov 2026, 7 of 7 support threads resolved

deactivated_plugin and update_option_active_plugins

Should be recorded through the option hook, which compares old and new lists

Simple History 5.36.0

98/100 from 493 ratings, 300,000+ installs, updated 17 Oct 2026, 3 of 4 threads resolved

deactivated_plugin

Likely missed

Activity Log 2.18.0

86/100 from 74 ratings, 200,000+ installs, updated 28 Oct 2026, 5 of 5 threads resolved

deactivated_plugin

Likely missed

Stream 4.5.0

86/100 from 76 ratings, 70,000+ installs, updated 12 Nov 2026, 0 of 1 threads resolved

deactivate_plugin (the “before” hook, also skipped when silent)

Likely missed

“Likely missed” is our reading of the code, not a test on a live site. We did not install each plugin and trigger a silent deactivation, so treat the last column as a lead to verify, not a verdict on the plugin. A plugin that watches the option is a better fit for this specific problem. The others still log the normal case, someone clicking Deactivate, and that has value of its own.

How do I get alerted the next time?

Use two layers: a must-use plugin inside WordPress that watches the option, and a scheduled check outside WordPress for the cases where no WordPress code ran.

Inside WordPress: a must-use plugin

WordPress fires update_option_active_plugins whenever that value changes, passing the old and new lists. Hooking it catches the dashboard click, the silent missing-file cleanup, an interrupted update and WP-CLI alike. Save this as wp-content/mu-plugins/active-plugins-watch.php. Must-use plugins load before normal plugins and cannot be switched off from the Plugins screen, which is what you want from a watcher. Our must-use plugins guide covers how they load.

<?php
// Checked on 15 Nov 2026: php -l clean, diff logic run against stubs. Not run on a production site.
/**
 * Plugin Name: Active Plugins Watch
 * Description: Logs and emails every change to the list of active plugins.
 */

add_action( 'update_option_active_plugins', 'tw_active_plugins_changed', 10, 2 );

function tw_active_plugins_changed( $old, $new ) {
	$old     = is_array( $old ) ? $old : array();
	$new     = is_array( $new ) ? $new : array();
	$removed = array_values( array_diff( $old, $new ) );
	$added   = array_values( array_diff( $new, $old ) );

	if ( ! $removed && ! $added ) {
		return;
	}

	$user = function_exists( 'wp_get_current_user' ) ? wp_get_current_user() : null;

	// Which code asked for the change. Function names only.
	$trace = array();
	foreach ( debug_backtrace( DEBUG_BACKTRACE_IGNORE_ARGS, 14 ) as $frame ) {
		$trace[] = ( isset( $frame['class'] ) ? $frame['class'] . '::' : '' ) . $frame['function'];
	}

	$context = array(
		'time'    => gmdate( 'c' ),
		'removed' => $removed,
		'added'   => $added,
		'user'    => ( $user && $user->exists() ) ? $user->user_login : 'none',
		'via'     => ( defined( 'WP_CLI' ) && WP_CLI ) ? 'wp-cli' : ( wp_doing_cron() ? 'cron' : ( wp_doing_ajax() ? 'ajax' : 'web' ) ),
		'request' => isset( $_SERVER['REQUEST_URI'] ) ? esc_url_raw( wp_unslash( $_SERVER['REQUEST_URI'] ) ) : '',
		'ip'      => isset( $_SERVER['REMOTE_ADDR'] ) ? sanitize_text_field( wp_unslash( $_SERVER['REMOTE_ADDR'] ) ) : '',
		'trace'   => implode( ' < ', $trace ),
	);

	error_log( 'active_plugins changed: ' . wp_json_encode( $context ) );

	// Email only when something was switched off.
	if ( $removed ) {
		wp_mail(
			get_option( 'admin_email' ),
			'[' . wp_parse_url( home_url(), PHP_URL_HOST ) . '] Plugin deactivated: ' . implode( ', ', $removed ),
			wp_json_encode( $context, JSON_PRETTY_PRINT )
		);
	}
}

How to read the log line:

  • validate_active_plugins in the trace, with a request to /wp-admin/plugins.php: Cause 1, a missing file.
  • deactivate_plugin_before_upgrade in the trace: the non-JavaScript update path. A matching “added” entry should follow seconds later. If it does not, the reactivation never ran.
  • via: wp-cli: a script or a person on the server.
  • Another plugin’s function names in the trace: Cause 3, and you now know which plugin.

Two adjustments worth making. Send the email to an address a person reads, since admin_email is often stale. And if your site sends mail unreliably, replace wp_mail() with a call to your team chat’s incoming webhook using wp_remote_post(). On multisite, network-activated plugins live in a site option, so add a second hook on update_site_option_active_sitewide_plugins. Its callback receives the option name first, then the new value, then the old value, so the argument order differs from the hook above.

Outside WordPress: a scheduled check

The must-use plugin cannot see a restored database or a stale cache, because no WordPress code ran. For those you need something that asks, on a schedule, whether the plugins you depend on are active.

#!/usr/bin/env bash
# Checked on 15 Nov 2026. required-plugins-check.sh: run from cron every 10 minutes.
# Prints (and so emails, under cron) only when something is wrong.
WP_PATH=/path/to/wordpress
REQUIRED="woocommerce elementor"   # slugs this site cannot run without

for p in $REQUIRED; do
  if ! wp --path="$WP_PATH" plugin is-active "$p" 2>/dev/null; then
    echo "$(date -u +%FT%TZ) $(hostname): required plugin NOT active: $p"
  fi
done

# Only meaningful while a recovery mode session exists
paused=$(wp --path="$WP_PATH" option list --search='*_paused_extensions' --field=option_name 2>/dev/null)
[ -n "$paused" ] && echo "$(date -u +%FT%TZ) $(hostname): paused extensions present: $paused"
# crontab -e
MAILTO=you@example.com
*/10 * * * * /usr/local/bin/required-plugins-check.sh

wp plugin is-active exits 0 when the plugin is active and 1 when it is not, which is what makes the test work. The WP-CLI docs add that if a plugin no longer exists but is still listed as active, the command warns, which helps with Cause 1 before anyone opens the Plugins screen. For a fleet, run the same loop over your WP-CLI aliases and keep each site’s required list in a small file.

Pair it with a check a visitor would notice. A page builder that is switched off still returns status 200, so an uptime monitor reports all clear while every page shows unstyled text. Request one page and look for a string only that plugin produces:

curl -s https://example.com/ | grep -q 'elementor-element' || echo "builder markup missing on home page"

Could the site be compromised?

Possibly, and the plugin that went off tells you how worried to be. A caching or SEO plugin switching off after an update is usually mechanical. A firewall, scanner or login-protection plugin switching off with no explanation deserves a compromise check before you turn it back on.

Look for the signs that do not depend on the plugin you just lost:

# Checked on 15 Nov 2026 (read-only)
# Core files that differ from the official release
wp core verify-checksums

# Plugins from WordPress.org whose files differ from the published copy
wp plugin verify-checksums --all

# Administrators, newest first
wp user list --role=administrator --fields=ID,user_login,user_email,user_registered --orderby=user_registered --order=DESC

# PHP files where none should be
find wp-content/uploads -name '*.php' 2>/dev/null

# Scheduled events you do not recognise
wp cron event list --fields=hook,next_run_relative

Also open wp-content/mu-plugins/, because a file you did not put there loads on every request and cannot be deactivated from the dashboard. Checksum checks only cover plugins hosted on WordPress.org, so a commercial plugin needs a fresh download to compare against. Our hidden admin account audit walks through the user and persistence checks in detail. If you find an unknown administrator or PHP in uploads, stop troubleshooting the plugin and treat the site as breached.

Common mistakes people report

These come from support threads and vendor documentation we read on 15 Nov 2026. We paraphrase them, and each thread is dated because older ones may not reflect current core.

  • Reactivating and moving on. In an Ultimate Member thread (posted around 2024, closed for inactivity), the owner found the plugin off with nothing in the activity log, reactivated it and asked whether others saw the same. The only suggestion was server resource limits, and no cause was confirmed. Without a watcher in place the next occurrence teaches you nothing either.
  • Assuming a failed update touched only one plugin. MainWP’s troubleshooting page lists server limits, security or caching plugin conflicts, a firewall blocking the package and file permissions as causes of an incomplete or missing plugin folder. The fix is the environment, not the updater.
  • Turning off auto-updates as the cure. In an April 2025 Strong Testimonials thread, a fatal error about an undefined method took the plugin down on PHP 7.4.33 and WordPress 6.7.2. Support advised a clean reinstall, deactivating and deleting without pressing “Uninstall” so data is kept, plus updating the outdated versions. The reporter also switched auto-updates off, which removes the rollback described above.
  • Blaming one plugin without proof. A 2016 thread described 11 of 23 plugins switching off at intervals ranging from 15 minutes to a few hours. The owner traced it by elimination to one plugin and its add-on, and the outcome was never reported. A watcher with a stack trace would have named the culprit instead of leaving a guess.
  • Treating an all-plugins-at-once event as an update problem. In a 2018 thread every plugin went off about once a week. A reply pointed out that a failed update normally hits only the plugin being updated, and suggested someone with control panel access, a faulty updater or a host-level cause. Everything at once points to the stored list or the plugins folder, so check Cause 4 first.
  • Forgetting the host’s own list. WP Engine’s disallowed plugins page says listed plugins are removed eventually after a notice. A site owner who never read the notice sees a plugin vanish and a deactivation notice follow. Read your host’s list and notices before you chase a bug.

One-page diagnosis order

  1. wp plugin list and ls wp-content/plugins: deactivated, paused or missing?
  2. Plugin file dates: did the files change at the time of the incident?
  3. wp-content/upgrade/, upgrade-temp-backup/, .maintenance: leftovers from an interrupted update?
  4. Access log: update.php and plugins.php?action=deactivate requests with IP and time.
  5. PHP error log: timeouts, memory limits and fatal errors in the same minute.
  6. Admin inbox for the recovery mode email, and the paused extensions option if a session exists.
  7. Database value against the value WordPress reads, and the dates of the last restore or staging push.
  8. Host activity log, management tool history and your host’s disallowed list.
  9. grep for deactivate_plugins( in installed code.
  10. If the plugin was a security plugin, run the compromise checks before anything else.

Questions people ask

Why did my WordPress plugin deactivate itself?

The common causes are a missing plugin file, an update interrupted after WordPress switched the plugin off, a host or another plugin deactivating it, an overwritten database value, or a fatal error. Checking whether the plugin’s files exist and when they last changed narrows it to one or two quickly.

Does WordPress log who deactivated a plugin?

No. Core keeps no activity log. Many logging plugins rely on the deactivated_plugin hook, which does not fire for silent deactivations. Watching the active_plugins option is more reliable.

Is a paused plugin the same as a deactivated one?

No. A paused plugin stays in the active list and is skipped on load, and only within a recovery mode session. A deactivated plugin has been removed from the list.

Will WordPress email me when a plugin breaks the site?

Only for fatal errors on protected endpoints such as the admin and login page, at most once a day by default, to RECOVERY_MODE_EMAIL or the admin email. A fatal error on a public page sends nothing.

What does “The plugin has been deactivated due to an error: Plugin file does not exist” mean?

An admin opened the Plugins screen and WordPress could not find that plugin’s main file, so it removed it from the active list. Reinstall the plugin and activate it.

How do I get an alert when a plugin is deactivated?

Use two checks. A must-use plugin hooked to update_option_active_plugins logs and emails every change from inside WordPress. A scheduled script running wp plugin is-active for the plugins the site depends on catches database-level changes from outside.

My security plugin was deactivated and I did not do it. Should I worry?

Treat it as suspect until you have ruled out a compromise. Check for unknown administrators, PHP files in uploads and changed core files before you reactivate it.

If plugins keep switching off across a group of sites and you want the cause found and monitoring set up, our WordPress care plans cover updates and monitoring, and we also take on one-off investigations. For a single site, the watcher above costs nothing and will usually name the cause on the next occurrence.

Part of the Wbcom Designs family

The all-in-one WordPress community stack

Also ours: wbcomdesigns.comvapvarun.combrndle.com