Last modified: 2013-02-17 08:08:05 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T26969, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 24969 - Protected threads in LiquidThreads give almost no indication that they're protected
Protected threads in LiquidThreads give almost no indication that they're pro...
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
LiquidThreads (Other open bugs)
unspecified
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2010-08-28 16:45 UTC by MZMcBride
Modified: 2013-02-17 08:08 UTC (History)
2 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---

Attachments
A screenshot of a protected LiquidThreads thread. (89.01 KB, image/png)
2010-08-28 16:45 UTC, MZMcBride 		Details
Add an attachment (proposed patch, testcase, etc.)

Description MZMcBride 2010-08-28 16:45:43 UTC 
Created attachment 7658 [details]
A screenshot of a protected LiquidThreads thread.

After a thread is protected in LiquidThreads, the only text that changes for admins is the "[Protect]" link becoming "[Unprotect]". There should be a better warning for admins that they're editing a protected thread.

Screenshot attached.
Comment 1 Brandon Harris 2010-09-09 17:13:37 UTC 
Taking this bug; requires design work.
Comment 2 Andre Klapper 2013-01-09 13:24:57 UTC 
Brandon:
This report has been in ASSIGNED status for more than one year and you are set as its assignee. In case that you are not actively working on a fix, please reset the bug status to NEW/UNCONFIRMED.
In case you do not plan to work on a fix in the near future: Please also edit the "Assigned To" field by clicking "Reset Assignee to default", in order to not prevent potential contributors from working on a fix. Thanks for your help!
[assigned>=1y]
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links