If a PHP upgrade broke WordPress, record the previous and current PHP versions, the exact error and when it appeared. Preserve a recovery point and use the error logs to identify an incompatible component before changing unrelated settings.
For broader outage symptoms, start with our WordPress website not loading guide.
Before upgrading PHP on a production WordPress site, check the current WordPress core, theme and critical plugins for compatibility. Older custom code may rely on behaviour removed or changed in newer PHP releases. A staging copy is the safest place to expose those incompatibilities before customers see them.
A blank page or generic critical-error message does not identify the cause. Review the PHP or WordPress error log for the first relevant fatal error and the file path involved. That often points directly to a plugin, theme or custom function requiring an update or code change.
Returning temporarily to the previous supported PHP version can restore service while the incompatible component is corrected. Do not leave an obsolete PHP release in place indefinitely. Once the root cause is fixed, retest the newer version on staging and verify forms, admin functions, scheduled tasks and other important features.
Compatibility problems can hide in functions that are not used on every request. After an upgrade, test forms, search, login, page-builder editing, ecommerce actions, scheduled tasks, API integrations and any custom code important to the business. Review logs again after testing because warnings or deprecations may reveal future problems even when the visible page appears normal.
Keep a short record of the incompatible component, the repair and the tests completed. Before another version change, verify your recovery copy using the WordPress backup guidance, which covers both files and the database.