IT Toolbox
Guide

How to recover WordPress after a plugin critical error

When wp-admin is inaccessible after the, activation or update of a plugin, the safest way is to disable only the suspicious plugin via the file system.

TopicWordPress →
⌚ About 2 min read
View my favorites
WordPress Intermediate. 15 min.

When wp-admin is inaccessible after the, activation or update of a plugin, the safest way is to disable only the suspicious plugin via the file system.

Avant de commencer : adaptez toujours les commandes et manipulations à votre environnement. Sur un système de production, prévoyez une backup ou un retour arrière lorsque l’action peut modifier la configuration.

Étapes à suivre

  1. 1

    Identify plugin

    Find the latest extension enabled or updated.

  2. 2

    Rename folder

    Via FTP or the file manager, rename only the plugin folder.

  3. 3

    Retester wp-admin

    WordPress will disable the missing extension.

  4. 4

    Read the PHP error

    Check the log to identify the incompatible function, class or version.

  5. 5

    , to a corrected version

    Remit the plugin only after validation.

À retenir

  • Do not rename the entire plugins folder if only one plugin is suspicious.
  • Keep WP_DEBUG_Dis PlaY disabled in production.
  • A PHP lint does not detect all the errors that appear only, at execution.
← All les guides
Technical deep dive

WordPress: deepen diagnosis without hiding the root cause

Technical checkpoints

  • WP_DEBUG_LOG usually writes to wp-content/debug.log only when WP_DEBUG is enabled and the PHP process can write the file.
  • Renaming a plugin directory prevents it from loading without changing the database, which is useful when wp-admin is unavailable.
  • WP_MEMORY_LIMIT cannot exceed the memory actually granted by PHP/hosting; memory errors require reading memory_limit and peak usage.

Controlled recovery

Isolate the failing plugin or layer, keep logs, then re-enable one component at a time.

define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);

Topic-specific pitfalls

  • Deleting .maintenance, a plugin or cache without recording initial state can make the symptom disappear without explaining the cause.
  • A redirect loop can come from WordPress, proxy/CDN, HTTPS or a plugin: check each layer separately.

How to validate

  • The site loads with clean logs and the failing component is identified, not merely disabled.
  • Temporary debug constants are removed or adjusted after the intervention.
♡ 0