574024 - Read-only mode

Status: VERIFIED FIXED

(addons.mozilla.org Graveyard :: Public Pages, defect)

Description

[Jeff Balogh (:jbalogh)]

fligtar: I started playing with read-only mode and need some content from you.  Please reassign this bug to me when you're done.

Here's the user-visible changes I have so far:
1. Login/register information is gone.  The only thing in the top bar is "Other Applications".

2. All inputs in form[method=post] are disabled and a message is inserted above the form (with js).  The message is: ____.

3. When a POST request is detected it is not allowed to continue down into the view function.  I'd like show a page that says something about "Use the back button and try again later."  The full message is: ____.

4. When something happens inside a GET view that triggers a write (which shouldn't happen, but I'm covering the bases here), we have middleware that catches the exception and says something about "oops...we tried to write."  The full message is: ____.  This could be the normal oops page, but I think a custom message would be considerate here.

Comment 1

[Justin Scott [:fligtar]]

(In reply to comment #0)
> Here's the user-visible changes I have so far:
> 1. Login/register information is gone.  The only thing in the top bar is "Other
> Applications".
> 
I think this is only okay if we have a message on every page saying we're in read-only mode and some features are disabled. Otherwise, people will be hunting for how to log in / register and never find it. If we do this, the message should be:

"Some features are temporarily disabled while we perform website maintenance. We'll be back to full capacity shortly."

> 2. All inputs in form[method=post] are disabled and a message is inserted above
> the form (with js).  The message is: ____.
> 
"This feature is temporarily disabled while we perform website maintenance. Please check back a little later."

> 3. When a POST request is detected it is not allowed to continue down into the
> view function.  I'd like show a page that says something about "Use the back
> button and try again later."  The full message is: ____.
> 
"This feature is temporarily disabled while we perform website maintenance. Please use your browser's Back button and try again a little later."

> 4. When something happens inside a GET view that triggers a write (which
> shouldn't happen, but I'm covering the bases here), we have middleware that
> catches the exception and says something about "oops...we tried to write."  The
> full message is: ____.  This could be the normal oops page, but I think a
> custom message would be considerate here.
>
"Some features on this page are temporarily disabled while we perform website maintenance. Please try again a little later."

Comment 2

[Jeff Balogh (:jbalogh)]

(In reply to comment #1)
> (In reply to comment #0)
> > Here's the user-visible changes I have so far:
> > 1. Login/register information is gone.  The only thing in the top bar is "Other
> > Applications".
> > 
> I think this is only okay if we have a message on every page saying we're in
> read-only mode and some features are disabled. Otherwise, people will be
> hunting for how to log in / register and never find it. If we do this, the
> message should be:
> 
> "Some features are temporarily disabled while we perform website maintenance.
> We'll be back to full capacity shortly."

That's what the admin site notice is for, in theory.

Comment 3

[Jeff Balogh (:jbalogh)]

http://github.com/jbalogh/zamboni/commits/b3dca77

QA: We can switch this on whenever you're ready.  You won't be able to log in or change data from zamboni, but browsing and installing should not be affected.

Comment 4

[Stephen Donner [:stephend] Not actively reading bugmail]

Verified FIXED; we filed a couple small bugs (bug 575455 and bug 575458), but nothing too major.