You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 12, 2022. It is now read-only.
Summarize the issue (briefly)
If a user's site is down due to a fatal error and they are trying to enter recovery mode, the password module should not perform any checks or provide any notifications to users.
The first priority in this scenario is to get out of their way entirely to allow them to fix the problem and get their site back online. If they're displayed the insecure password screen, they'll likely just dismiss it and get frustrated, and definitely won't take the time to actually change their password.
Steps to reproduce
Create a fatal error on a site.
Delete the nfd_sp_next_notice user meta entry for the user.
Attempt to enter recovery mode.
See the insecure password screen.
Expected behavior
Screenshots
Bluehost Plugin Version:
Version: 2.12.5
Browser (with version) & Operating System (with version)
Browser:
Operating System:
Device:
Additional context
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Summarize the issue (briefly)
If a user's site is down due to a fatal error and they are trying to enter recovery mode, the password module should not perform any checks or provide any notifications to users.
The first priority in this scenario is to get out of their way entirely to allow them to fix the problem and get their site back online. If they're displayed the insecure password screen, they'll likely just dismiss it and get frustrated, and definitely won't take the time to actually change their password.
Steps to reproduce
nfd_sp_next_notice
user meta entry for the user.Expected behavior
Screenshots
Bluehost Plugin Version:
Browser (with version) & Operating System (with version)
Additional context
The text was updated successfully, but these errors were encountered: