- Home
- Skills
- APIs & Backend
- wordpress-rescue
Wordpress Rescue
Diagnose WordPress errors from the actual debug.log and fix them with a safe rollback.
$15
Works with the AI Agents you already use
wordpress-rescue
Example session with this skill installed
The site is showing a white screen after I updated some plugins. I have the wp-content/debug.log file. What is the cause and how do I fix it safely?
- Read your context and instructions
- Compiled the wordpress-rescue
I have analyzed the symptoms and the provided log information. The site is experiencing a fatal PHP error caused by a specific plugin conflict.
WordPress Rescue Diagnosis
| Metric | Details |
|---|---|
| Error Type | PHP Fatal Error: Call to undefined function |
| Source File | /wp-content/plugins/sample-booking-form/includes/booking.php |
| Line Number | 87 |
| Suspected Cause | Partial plugin update or missing dependency in sample-booking-form |
| Primary Fix | Deactivate the plugin via WP-CLI or folder renaming |
| Rollback Step | Restore the sample-booking-form folder from your pre-fix backup |
Recommended Resolution Path
Safety Backup: Copy the directory /wp-content/plugins/sample-booking-form/ to /wp-content/plugins/sample-booking-form.backup before proceeding.
2.
Isolation: Rename the active plugin folder to sample-booking-form.off. This will force WordPress to deactivate the plugin.
3. Verification: Refresh the website. If the White Screen is gone, the plugin was the sole cause.
4.
Reinstallation: Delete the broken plugin folder and upload a fresh copy of the plugin from a known stable version.
5. Final Check: Reactivate the plugin and check the debug.log to ensure no new warnings appear.
Next steps
- Access your server via FTP or File Manager to rename the folder.
- Check if a PHP version update on the server recently occurred, as this may have triggered the incompatibility.
- If the error persists after renaming, provide the server error log for further analysis.
Connects securely to your tools. The creator never sees your data.
About this skill
WordPress sites fail for dozens of reasons, and guessing at the cause turns a minor bug into a permanent outage. This skill replaces trial and error with log-based diagnostics, ensuring every fix is backed by a specific line in debug.log. It provides a structured protocol for recovery that prioritizes site stability and rollback readiness.
What it does
- Log-driven diagnosis identifies the exact file, line, and plugin causing fatal errors or white screens.
- Database error resolution decodes MySQL connection failures by verifying
wp-config.phpagainst server status. - Conflict isolation provides step-by-step sequences for deactivating plugins or themes via WP-CLI or filesystem renaming.
- Environment auditing checks for PHP version mismatches, memory limit exhaustion, and file permission bottlenecks.
- Systematic rollbacks enforces a backup-first workflow to ensure any failed fix can be instantly reverted.
How it works
- Enable logging by configuring
WP_DEBUGandWP_DEBUG_LOGinwp-config.phpto capture the specific failure. - Analyze the log from the bottom up to isolate the most recent fatal error and identify the responsible file path.
- Execute the decision tree to match the log entry against known fixes for redirect loops, 500 errors, or plugin conflicts.
- Apply and verify the fix one change at a time, testing both the front end and admin dashboard.
Frameworks & tools
This skill works with WordPress Core, WP-CLI, and standard LAMP/LEMP stacks. It requires access to wp-config.php, the wp-content directory, and server-level error logs.
Why this beats prompting it yourself
Generic AI prompts often suggest "clear your cache" or "reinstall WordPress" as first steps, which can lose data or hide the root cause. This skill enforces a "log-first" rule that prevents destructive guessing and ensures you only touch the files that are actually broken.
Use cases
- Fixing a White Screen of Death after a bulk plugin update.
- Resolving "Error Establishing a Database Connection" after a server migration.
- Breaking out of a redirect loop caused by
.htaccesscorruption. - Restoring admin dashboard access when a plugin conflict locks you out.
Known limitations
Cannot fix errors that occur before wp-config.php is loaded unless server-level logs are provided. Physical file access via FTP, SSH, or a file manager is required to apply fixes.
Requires file-level access (FTP/SSH) or WP-CLI. Cannot diagnose errors occurring before wp-config.php loads without server logs. Empty logs require manual force-logging setup.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed today
Requires