IT Toolbox
IT Toolbox

WordPress Center

WordPress / PHP / Web

WordPress Center

Diagnose common WordPress incidents and find useful checks, commands and settings without directly modifying your site.

Analyse locale de wp-config.php

Le contenu est analysé uniquement dans votre navigateur. Les valeurs de DB_PASSWORD, clés et salts ne sont jamais affichées dans le rapport.

Diagnostic express

Diagnostic Version WordPress
wp core version
Diagnostic Check les fichiers du cœur
wp core verify-checksums
Plugins Lister les plugins
wp plugin list
Plugins Lister les plugins actifs
wp plugin list --status=active
Plugins Simuler les mises à jour
wp plugin update --all --dry-run
Thèmes Lister les topics
wp theme list
Thèmes Simuler les mises à jour
wp theme update --all --dry-run
Base Check la base
wp db check
Base Taille de la base
wp db size
URLs Adresse WordPress
wp option get siteurl
URLs Adresse du site
wp option get home
Permaliens Lister les règles rewrite
wp rewrite list
Permaliens Régénérer les règles
wp rewrite flush --hard
Cron Lister les tâches
wp cron event list
Cron Tester WP-Cron
wp cron test
Config WP_DEBUG
wp config get WP_DEBUG
Config DISABLE_WP_CRON
wp config get DISABLE_WP_CRON
Cache Vider le cache objet
wp cache flush
Security Lister les administrateurs
wp user list --role=administrator
Security Check les checksums du cœur
wp core verify-checksums
Médias Régénérer les médias manquants
wp media regenerate --only-missing --yes
Recherche Dry-run changement URL
wp search-replace 'http://ancien-domaine' 'https://nouveau-domaine' --dry-run
Système Version PHP
php -v
Système Espace disque
df -h
Logs Suivre debug.log
tail -f wp-content/debug.log
1

Backupr avant

Avant une mise à jour majeure, un search-replace ou une réparation de base.

2

Logs avant intuition

Une erreur PHP exacte vaut mieux qu’une désactivation aléatoire de plugins.

3

WP-CLI

Très utile lorsque wp-admin ne répond plus.

4

Permaliens

Vérifiez aussi la configuration Apache/Nginx, pas seulement WordPress.

5

SMTP

From, enveloppe Sender, SPF/DKIM/DMARC et authentification doivent être cohérents.

6

Malware

Préservez les preuves et identifiez le vecteur avant de seulement supprimer les fichiers visibles.

Warning : certaines commandes WP-CLI peuvent modifier le site. Utilisez d’abord les variantes de diagnostic ou --dry-run lorsqu’elles existent, et conservez une backup récente.
Field troubleshooting

Center mission

8 playbooks

Troubleshoot WordPress by layers — HTTP/PHP, plugins/theme, database, cache, cron, mail and permissions — keeping a backup and avoiding multiple simultaneous changes.

Quick triage

  • Record exact URL, HTTP code, message and latest change.
  • Check frontend, wp-admin and PHP/DB health separately.
  • Collect error_log/debug.log before broad disabling.
  • Confirm disk space and database availability.
  • Back up files/database before structural change.

Decision tree

Critical error / 500→

Start with PHP logs and latest plugin/theme/change.

DB connection error→

Test MySQL, credentials, host and saturation.

Site slow→

Measure TTFB, queries, cron, cache and resources.

Form email fails→

Separate WordPress generation from SMTP delivery.

Intervention playbooks

Start read-only, collect evidence, then change one variable at a time.

01WordPress critical errorControlled change
Symptom

“There has been a critical error” screen or wp-admin unavailable after a change.

Checks

  • Read PHP fatal with exact file/line.
  • Identify latest plugin/theme/update.
  • Check PHP version and compatibility.

Commands / evidence

wp plugin listwp theme listtail -n 100 wp-content/debug.log

Expected result

Fatal points to a specific component or incompatibility.

Corrective actions

  • Disable only failing component then retest.
  • Keep logs and version before update/rollback.

Escalate when

Fatal in core, corruption or critical business plugin with no alternative.

02HTTP 500 errorControlled change
Symptom

Server returns 500 on whole site or specific routes.

Checks

  • Read PHP/Apache/Nginx error log at timestamp.
  • Check .htaccess/rewrite and PHP memory.
  • Compare frontend and direct endpoint.

Commands / evidence

wp core verify-checksumsphp -vwp option get siteurl

Expected result

500 is tied to identifiable fatal, rewrite, permission or resource issue.

Corrective actions

  • Fix identified layer without blindly rewriting all .htaccess.
  • Retest exact route after each change.

Escalate when

500 comes from server/host or multiple vhosts are affected.

03White screen / empty outputRead-only
Symptom

Blank page with no message while server responds.

Checks

  • Enable logging without displaying errors in production.
  • Look for fatal, memory exhausted or output buffering.
  • Test theme/plugin in controlled environment.

Commands / evidence

wp config get WP_DEBUGwp plugin list --status=activewp theme list

Expected result

A log explains why rendering stops.

Corrective actions

  • Fix responsible component or limit.
  • Do not leave WP_DEBUG_DISPLAY enabled in production.

Escalate when

No log despite PHP request or FPM/server crash.

04Database connection errorIntrusive / escalation
Symptom

“Error establishing a database connection” or SQL queries impossible.

Checks

  • Test MySQL host/port and database service.
  • Check DB_NAME/USER/HOST without exposing password.
  • Check connections, space and DB health.

Commands / evidence

wp db checkwp config get DB_HOSTmysqladmin ping -h <dbhost>

Expected result

WordPress authenticates and wp db check accesses tables.

Corrective actions

  • Fix availability/credentials with backup before any table repair.
  • Do not run repair without evidence of corruption.

Escalate when

InnoDB corruption, saturated SQL server or critical data affected.

05Plugin or theme conflictControlled change
Symptom

Feature breaks after activation/update or only with component combination.

Checks

  • Reproduce with latest identified change.
  • Check versions and PHP/WordPress dependencies.
  • Compare staging environment if available.

Commands / evidence

wp plugin listwp theme listwp core version

Expected result

Conflict is reproducible with a specific component or version.

Corrective actions

  • Targeted rollback/update and test before production.
  • Avoid mass disabling on live site.

Escalate when

Essential business plugin or conflict requires code change.

06Slow WordPress siteRead-only
Symptom

High TTFB, slow wp-admin or CPU/SQL spikes.

Checks

  • Measure frontend, admin and static request separately.
  • Check cron, slow queries, autoload and heavy plugins.
  • Check cache and hosting resources.

Commands / evidence

wp cron event list --due-nowwp option list --autoload=on --format=total_byteswp plugin list

Expected result

Slowness is attributed to PHP, SQL, cron, plugin or external layer.

Corrective actions

  • Optimize measured cause, not only add cache.
  • Test before/after with same URL and conditions.

Escalate when

Hosting SQL/CPU budget reached, slow business query or infrastructure incident.

07WordPress forms / email not receivedControlled change
Symptom

Form submits but notification is missing or lands in spam.

Checks

  • Check whether WordPress actually generates email.
  • Check SMTP/plugin, sender and domain authentication.
  • Test an external mailbox and inspect SMTP logs.

Commands / evidence

wp plugin list | grep -i smtpwp option get admin_emailnslookup -type=txt <domaine>

Expected result

Message is generated, accepted by SMTP and traceable to recipient.

Corrective actions

  • Configure authenticated SMTP and coherent domain From.
  • Treat SPF/DKIM/DMARC deliverability separately from form logic.

Escalate when

Third-party mail service rejects, domain authentication is wrong or form plugin does not trigger hook.

08Permissions / update failureControlled change
Symptom

WordPress cannot write plugins, uploads or perform an update.

Checks

  • Read owner/group/mode on affected paths.
  • Identify PHP-FPM/Apache user.
  • Check disk space and FS_METHOD.

Commands / evidence

ls -ld wp-content wp-content/uploads wp-content/pluginswp core verify-checksumsdf -h

Expected result

Web process has only required rights on expected paths.

Corrective actions

  • Fix minimum ownership/mode, never chmod -R 777.
  • Back up before core/plugin update.

Escalate when

Hosting requires special permissions, filesystem is read-only or compromise is suspected.

End-of-intervention checklist

  • Retest frontend, wp-admin and initially affected feature.
  • Check logs for no new fatal.
  • Confirm backup after change where appropriate.
  • Document changed plugin/theme/configuration.
  • Remove any temporary displayed debug mode.

Continue in BAOI

Related cheat sheetWordPress — express troubleshooting IT toolsCalculate, inspect or generate without leaving the workflow. ProceduresFollow a controlled implementation procedure. Known failuresCross-check the symptom with known failure patterns.
♡ 0