When you take your site offline / put it into maintenance mode, you can still login via /user. However, if you enter incorrect login details (username/password combo), you get returned to the "Site Offline" page, with no indication of what went wrong. Is there a way to set it up so that a 403 error can still be returned correctly when the site is offline?

Steps to replicate

  1. Set the site into offline/maintenance mode
  2. Logout
  3. Visit the front page to ensure maintenance mode is on correctly
  4. Go to /user and provide an incorrect username and password
  5. Find yourself back at the mainetance mode splash page with no errors as to what happened

I haven't tested this in D7, but I assume it will be a problem there too.

Comments

dbeall’s picture

I am not sure what you want it to do.. that behavior is normal due to maintenance mode..

wretched sinner - saved by grace’s picture

What would be good is some feedback that the username/password is incorrect, and on a successful logon maybe to indicate that so that they know what is happening.

dbeall’s picture

That will happen if the site is on-line..It will pop a message "sorry, unrecognized username or password"

wretched sinner - saved by grace’s picture

I am aware of that - what I think would be worthwhile is, when the site is offline to have the same message come up. That way if a user At this stage only UID 1, but in future with permissions for other users to access the site when it is offline (#201415: Add permission to access site in maintenance mode) then they will need feedback on username/password errors.

Anonymous’s picture

I just tried to replicate the problem in Drupal 6.9 and 6.13dev, but the incorrect login message appears like normal. If I try to create a new account or request a password reset, then it does redirect me to the site offline screen as expected.

wretched sinner - saved by grace’s picture

Status: Active » Postponed (maintainer needs more info)

Hmm - I will check again. It may have been an anomoly

dpearcefl’s picture

Status: Postponed (maintainer needs more info) » Closed (won't fix)

Closing this issue because of a lack of activity.