WordPress “Call to Undefined Function” Fatal Error: Dependency or Load Order?
The code called a function that was never loaded in that request. Identify the caller, expected provider and load order.
WORDPRESS RESCUE JOURNAL
Understand the symptom.
Decide without making it worse.
Specialist-reviewed guides for broken, compromised or blocked websites. Diagnosis, security and practical decisions without blind recipes.
START WITH THE VISIBLE SYMPTOM
WordPress repair guidance organised by incident.
These guides help you preserve evidence, avoid risky shortcuts and decide when the problem needs a controlled technical intervention.
01
WordPress critical error
Understand the fatal error behind the generic message and the evidence worth preserving before changing plugins or themes.
Open the guide 02WordPress white screen
Learn why a blank page should be diagnosed through protected logs instead of exposing debug information publicly.
Open the guide 03Malicious redirects
See where conditional redirects hide and why clearing one server rule may not remove the infection.
Open the guide 04WordPress admin lockout
Separate a legitimate access problem from signs of compromise and recover control without leaving a bypass.
Open the guide 05A plugin update broke the site
Compare rollback, compatibility repair and safe update routes when production fails after a release.
Open the guide 06WooCommerce checkout failure
Trace the sales journey from browser and session through payment callback, order creation and stock.
Open the guideExplore: Errores y diagnóstico
Errors & Diagnosis
Malware & Security
Malware y seguridad
Recovery & Prevention
Recuperación y prevención
WooCommerce Critical
WooCommerce crítico
Read the guide ↗
WordPress “Headers Already Sent” Warning: Find the First Output
Headers already sent means PHP produced output before WordPress tried to send cookies, redirects or HTTP headers. The first-output file and line are the clue.
WordPress “Failed to Open Stream: Permission Denied” — Ownership Before chmod
Permission denied names a file operation the PHP user could not perform. Check owner, group, ACL and mount mode before changing numbers.
WordPress “Missing a Temporary Folder” Error: Find the Real PHP Path
Diagnose the WordPress “Missing a Temporary Folder” error without confusing PHP upload settings with WP_TEMP_DIR. Hosting checks and repair verification.
WordPress “The Link You Followed Has Expired”: Upload, Nonce and Limit Checks
This message usually hides an upload-size or nonce failure. The action and server limits identify which one.
WordPress WP-Cron Not Running: Fixing Missed Schedule and Stalled Tasks
Missed schedules mean the event queue is not being triggered or a task is failing. Separate trigger, lock and callback problems.
WordPress Loopback Request Failed: Why Site Health Cannot Call the Site
A failed loopback means the server cannot call its own public WordPress URL reliably. Test DNS, TLS, authentication and firewall layers.
WordPress cURL Error 60: SSL Certificate Problem — Safe Diagnosis and Repair
cURL error 60 means the server cannot verify the remote certificate chain. Fix trust or the remote chain; do not disable verification.
WordPress cURL Error 28: Connection Timed Out — How to Find the Slow Dependency
cURL error 28 means an outbound HTTP request exceeded its timeout. Find the destination and caller before raising limits.
WordPress REST API Returns 401 Unauthorized: Cookies, Nonces and Application Passwords
A 401 from wp-json is an authentication failure, not a routing failure. Identify which authentication method the request expected.
WordPress admin-ajax.php Returns 400 Bad Request: A Practical Diagnostic Guide
A 400 from admin-ajax.php often means a missing action, invalid nonce or malformed request. Capture the request before blaming the server.
WordPress “The Response Is Not a Valid JSON Response”: How to Find the Broken Layer
The block editor’s JSON error usually means the REST request returned HTML, a redirect or an error page. Trace the response before changing permalinks.