[Blueprints] Prevent WSOD when autologin is enabled and a plugin logs a notice #2079
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR ensures the autologin step won't cause a perpetual white screen of death when one of the plugins displays a notice.
The autologin flow consists of a bunch of checks, setcookie() call, a header('Location') call, and an
exit;
. However, when the headers are already sent, the cookies won't be set, the redirect won't work, but the script will still. This, effectively, prevents loading any WordPress page.This PR adds a
headers_sent()
check to stop the autologin step early in those scenarios when we can't finish the login.Testing instructions