Closed
Bug 603472
Opened 15 years ago
Closed 11 years ago
Read-only mode (or other site-wide) messaging
Categories
(support.mozilla.org :: General, defect, P4)
support.mozilla.org
General
Tracking
(Not tracked)
RESOLVED
FIXED
Future
People
(Reporter: jsocol, Unassigned)
Details
Attachments
(1 file)
|
59.65 KB,
image/png
|
Details |
Basically, what we're looking for is a decent way to display a global message. For read-only mode (bug 570284) AMO's solution was to stick a message in front of POST forms. This doesn't work for us because we use a number of small forms for things like moderator actions, which ends up with the message repeated several times in a row.
I looked at inserting text near the top of the page but couldn't find a decent place to do it.
The initial use case would be for read-only mode, where we'd display a message along the lines of one of these:
"Due to ongoing website maintenance, you are currently seeing a read-only version of this page."
"Due to ongoing maintenance, some features of this page are temporarily disabled."
Chowse, this is low priority, but when you have time, think you could help us out?
| Reporter | ||
Updated•15 years ago
|
Priority: P4 → P2
Target Milestone: 2.3 → Future
Updated•14 years ago
|
Assignee: chowse → nobody
Comment 1•12 years ago
|
||
Perhaps we could copy the way Bugzilla does it? Or look to their code for some reference? This would be nice to have considering we are doing read-only mode more often these days. Plus it'd save Ricky and Will from having to create a new thread in the Contributors forum every time the site was going into read only mode. :P
Updated•12 years ago
|
Priority: P2 → P4
Whiteboard: u=contributor c=general p= s=2013.backlog
Target Milestone: Future → 2013Q2
Comment 3•11 years ago
|
||
We already have this for global announcements, out of date warnings, etc.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Comment 4•11 years ago
|
||
remove sprint metadata
Whiteboard: u=contributor c=general p= s=2013.backlog
You need to log in
before you can comment on or make changes to this bug.
Description
•