Last modified: 2007-07-18 18:03:18 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 10630 - Mark (semi-)protected pages visibly
Mark (semi-)protected pages visibly
Status: RESOLVED DUPLICATE of bug 10347
Product: MediaWiki
Classification: Unclassified
Parser (Other open bugs)
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2007-07-18 12:51 UTC by Danny B.
Modified: 2007-07-18 18:03 UTC (History)
0 users

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


Description Danny B. 2007-07-18 12:51:20 UTC
Although (semi-)protected page might be recognizible by having "view source" instead of "edit" tab, it would be more user friendly to mark these pages somehow in more visible way.

This is currently being solved by including templates such as {{Protected}}, but its automatical solution would be handy, since anything done manually can cause it won't be synchronized with actual situation.

Ideas for solutions as collected from users suggestions:
* some kind of image (eg. lock) shown somewhere
* different color of header (page title)
* small line with text such as "this page is (semi-)protected", probably linking to protect log, in place where other additional infos are such as "redirected from foo" or links to parent pages
* any other...
Comment 1 Brion Vibber 2007-07-18 18:03:18 UTC

*** This bug has been marked as a duplicate of bug 10347 ***

Note You need to log in before you can comment on or make changes to this bug.