TopicWordPress →
⌚ About 2 min read
Quickly disable an extension that causes a fatal error when the WordPress administration is not more accessible.
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
Create a backup
Save files and database if possible.
-
2
Access the files of the site
Log in to FTP/SFTP or via the file manager.
-
3
Open wp-content/ Plugins
Find the folder of the suspicious extension.
-
4
Rename plugin folder
Add for example -disabled to the folder name.
-
5
Retester WordPress
If the site returns, then analyze compatibility and logs.
À retenir
- Do not remove the extension immediately: the rename makes it easier to go back.
- Enable WP_DEBUG only in a controlled manner and avoid public exposure of sensitive logs.
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
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.