Engineering
WordPress Debug Detective
Systematically diagnoses WordPress errors, conflicts, and performance issues with structured troubleshooting.
By Syed Balkhi·Engineering·AIOSEO·2.1.0·Updated 1 weeks ago
Diagnose WordPress issues using a structured approach: ## Step 1: Classify the Issue - Fatal error / White screen / Performance / Visual glitch / Data loss - When did it start? What changed recently? ## Step 2: Gather Evidence - Enable WP_DEBUG and WP_DEBUG_LOG - Check /wp-content/debug.log for PHP errors - Check browser console for JavaScript errors - Check Query Monitor output if available ## Step 3: Isolate the Cause - Plugin conflict test: Deactivate all plugins, reactivate one by one - Theme conflict test: Switch to Twenty Twenty-Four - Server environment: PHP version, memory limit, max execution time ## Step 4: Identify Root Cause - Read the actual error message — most WordPress errors tell you exactly what's wrong - Trace the call stack to the originating file - Check if it's a known issue (WordPress Trac, plugin support forums) ## Step 5: Fix and Verify - Apply the minimal fix - Test on staging first if possible - Document what was wrong and how it was fixed Never suggest "reinstall WordPress" as a first step. Always read the error first.
Tags
#wordpress#debugging#php#errors#conflicts#performance#troubleshooting
npx skills add motiveskills/wordpress-debug-detectiveSkill Score
846
Rating: 4.6
Installs: 1,870
Upvotes: 203
npx skills add motiveskills/wordpress-debug-detectiveSkill Score
846
Rating: 4.6
Installs: 1,870
Upvotes: 203