WordPress log not being created: find where errors are going
Is debug.log missing or empty in WordPress? Check configuration, the private path, and the PHP context, then verify logging without exposing errors.


Site appearance
A clear goal, steps in the right order and a result to verify.
Is debug.log missing or empty in WordPress? Check configuration, the private path, and the PHP context, then verify logging without exposing errors.
Is the WordPress API rejecting a parameter? Read rest_invalid_param details, check the schema, and correct the client’s format without disabling validation.
Does a WordPress request return rest_no_route? Find the REST root, check the route and HTTP method, then fix the client or component providing them.
Does your WordPress SFTP connection report a different SSH key? Verify the fingerprint for the correct server, then update only the affected trust entry.
Does the site work while WP-CLI reports an old PHP or missing module? Compare executables and INI files, then use the correct launcher.
Does your WordPress homepage show a file listing? Disable directory indexing, check the domain root, and restore the correct entry file.
Does a WordPress page fail despite status 200? Compare compressed responses, isolate the responsible layer, and restore consistent decoding.
Are WordPress installations and updates blocked? Check DISALLOW_FILE_MODS, correct the relevant configuration, or use the intended deployment process.
Is the Deactivate button missing in WordPress? Distinguish dependencies, network activation, and must-use plugins, then remove the correct loading mechanism on a copy.
Does a WordPress restore stop at “Unknown collation”? Compare the servers, then choose a compatible destination or an appropriate export.
Does a WordPress write exceed max_allowed_packet? Identify the affected data, reduce its growth, or adjust the SQL limit with proper checks.
Does WordPress keep asking for a database update? Check files and database, finish the schema upgrade, then check errors and caches.