Last modified: 2011-11-22 01:04:26 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 T15572, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 13572 - Special:Log search should be case-insensitive
Special:Log search should be case-insensitive
Status: NEW
Product: MediaWiki
Classification: Unclassified
Page protection (Other open bugs)
unspecified
All All
: Low enhancement with 3 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-03-31 21:12 UTC by mnh
Modified: 2011-11-22 01:04 UTC (History)
0 users

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


Attachments

Description mnh 2008-03-31 21:12:27 UTC
Basic synopsis: protection is case insensitive, log and unprotecting are not. The idea is sound, but may lead to admins having absolutely no clue what caused the block for a specific variant in the first place and thus whether unprotecting is actually a good idea.

How to reproduce: create-protect any page (say [[User:You/Test]]) and switch case for some letter in between, for example [[User:You/TeSt]]. Try to discover the log entry. Imagine a longer page name and some unknown Joe Random User asking you to unprotect it.

Solution: always attach the log entry to the all-lowercase variant. While this may lead to problems if this variant is eventually unprotected, this can hardly be avoided while preserving the present -- albeit somewhat laborious -- possibility to not protect a single variant. Unless you're willing to build O(2^{page name length}) log entries, that is.
Comment 1 Brion Vibber 2008-04-01 22:23:11 UTC
Changing summary to clarify.

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


Navigation
Links