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
When enabling "Everyone except Administrators" in the PAPC Maintenance Mode Settings on the Live site (and probably other environments), upon logging out and then accessing the wp-admin, the user sees "Briefly unavailable for scheduled maintenance. Check back in a minute."
Steps to Reproduce:
Install PAPC and deploy to Live
On Live, access wp-admin and go to Settings > Pantheon Page Cache
Set the Default Max Age to 604800 (1 week) if not already set
Under "Maintenance Mode", select "Everyone except Administrators"
Click "Save Changes"
Log out of wp-admin
Access wp-admin again
See message "Briefly unavailable for scheduled maintenance. Check back in a minute."
Since it happens on a Live site and .maintenance is not present in the wp root directory (and isn't delete-able if it were), the workaround to get back to "Disabled" maintenance mode is to run terminus wp -- $SITE.$ENV option delete pantheon-cache to disable that setting and regain access to wp-admin.
The text was updated successfully, but these errors were encountered:
jazzsequence
changed the title
Everyone except Administrators maintenance mode breaks wp-admin
[BUGS-8199] Everyone except Administrators maintenance mode breaks wp-admin
May 31, 2024
Problem:
When enabling "Everyone except Administrators" in the PAPC Maintenance Mode Settings on the Live site (and probably other environments), upon logging out and then accessing the wp-admin, the user sees "Briefly unavailable for scheduled maintenance. Check back in a minute."
Steps to Reproduce:
Since it happens on a Live site and .maintenance is not present in the wp root directory (and isn't delete-able if it were), the workaround to get back to "Disabled" maintenance mode is to run
terminus wp -- $SITE.$ENV option delete pantheon-cache
to disable that setting and regain access to wp-admin.The text was updated successfully, but these errors were encountered: