Halkali merkez neighborhood fatih st ozgur apt no 46 , Kucukcekmece , Istanbul , 34303 , TR
The first goal in WordPress recovery is not to hide the error, but to protect data and find the real PHP record. This hub connects backup, critical-error and white-screen workflows and shows which guide matches each symptom.
Turkey (Turkish)
Germany (German)
Worldwide (English)
PROTECT FIRST
wp db export ../before-repair.sql
THEN MEASURE
wp core version
php -v
tail -n 120 wp-content/debug.log
ISOLATE LAST
wp plugin status
wp theme statusBackup is not an error page; it is a data-protection and recovery process. A critical-error message and a fully white or empty page are not the same symptom. These guides have distinct purposes and descriptive internal links.
Back up database and files as one set; prove validity with checksums, off-site storage and a clean restore test.
Open guide →Fatal-error diagnosisIdentify faulty files, plugins, themes or version conflicts using Recovery Mode, debug.log and the PHP error log.
Open guide →Empty-response diagnosisUse status code, body size and log timestamps to isolate the empty output and determine whether scope is site-wide, wp-admin-only or one URL.
Open guide →Before changing anything, prepare a matching file+database backup, checksum and rollback procedure.
Review Recovery Mode email and debug.log/PHP error logs for the same time window.
Measure status code and body size with curl, then compare logs and scope.
Match the file archive and SQL dump with a timestamp or manifest. For transactional sites, consider a maintenance window or snapshot for consistency.
Keep WP_DEBUG_DISPLAY off in production and inspect details in debug.log or the PHP error log.
Record whether the issue affects the whole site, wp-admin, one URL or a particular user role.
Inspect the file path in the log and recent changes before blindly disabling everything. Re-test the same request after each step.
No. Both may stem from a PHP fatal error, but the visible symptom, HTTP response and diagnostic path differ. Critical errors may offer Recovery Mode; white screens first require confirming an actual empty response.
Protect the database, wp-content, wp-config.php and deployment-specific web-server rules. Keep the backup outside the web root and in a second location.
It may be used temporarily, but details must not be shown to visitors. Enable WP_DEBUG_LOG with WP_DEBUG_DISPLAY off and review settings after diagnosis.
It can be an emergency isolation method when admin and WP-CLI are unavailable, but back up first, record the change and account for the impact of disabling all plugins.
Contact Eka Software and Information Systems for installation, server, script and technical support services.