Closed
Bug 568355
Opened 16 years ago
Closed 16 years ago
'Thread Locked' message should not be visible to non-authenticated users.
Categories
(support.mozilla.org :: Forum, task)
support.mozilla.org
Forum
Tracking
(Not tracked)
VERIFIED
FIXED
2.1
People
(Reporter: vish_moz, Assigned: jgross)
References
()
Details
'Reply' link is visible for locked threads if you are logged-in.
STR:
1. log into SUMO stage
2. go to https://support-stage-new.mozilla.com/en-US/forums/test-forum/217
which is a locked thread
3. click on 'Reply'
4. Post some text and hit 'Reply'
Actual result:
You land on a plain page without CSS saying 'You Screwed Up'
Expected result:
'Reply' link should be disabled for locked threads.
| Assignee | ||
Updated•16 years ago
|
Summary: 'Reply' link should be disabled for locked threads → 'Thread Locked' message should not be visible to non-authenticated users.
| Assignee | ||
Comment 1•16 years ago
|
||
Actually, it isn't possible to reply to locked threads.
However, non-authenticated users can see 'This thread has been locked. It is no longer possible to post new replies,' when no message should be displayed.
| Assignee | ||
Updated•16 years ago
|
Assignee: nobody → jgross
| Reporter | ||
Comment 2•16 years ago
|
||
Scratch the description in comment 0.
locked threads should not display any message to unauthenticated users
STR:
1. go to SUMO stage (log-out if you are logged-in)
2. go to a locked thread like
https://support-stage-new.mozilla.com/en-US/forums/test-forum/217
Actual result:
You see the message 'This thread has been locked. It is no longer possible to
post new replies.'
Expected result:
Users who are not logged-in should not see this message.
| Reporter | ||
Comment 3•16 years ago
|
||
Correction once again.
You get the message 'This thread has been locked. It is no longer possible to
post new replies.' for any thread when you are logged-out not just the locked threads.
| Assignee | ||
Comment 4•16 years ago
|
||
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•