Last modified: 2010-05-15 15:38:40 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 T4874, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 2874 - Special namespace case sensitive when $wgCapitalLinks=false;
Special namespace case sensitive when $wgCapitalLinks=false;
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
All All
: Low normal with 2 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
: 5132 (view as bug list)
Depends on:
Blocks: 3950
  Show dependency treegraph
Reported: 2005-07-15 23:58 UTC by Connel MacKenzie
Modified: 2010-05-15 15:38 UTC (History)
1 user (show)

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


Description Connel MacKenzie 2005-07-15 23:58:40 UTC
Version 1.5beta3 works doesn't work.

Seems to be true for all things in Special: namespace.
Comment 1 Rowan Collins [IMSoP] 2005-07-16 00:45:43 UTC
Well, this is true for all pages in all namespaces, now that the English
Wiktionary has been switched over to fully case-sensitive mode - in the same way
that "[[log]]" is no longer the same as "[[Log]]", "[[Wiktionary:log]]" is not
"[[Wiktionary:Log]]" and "[[Special:log]]" is not "[[Special:Log]]". 

This is probably a little confusing, and even annoying, though, so perhaps the
Special namespace should be an exception in this regard, and ignore the value of
$wgCapitalLinks - especially since, unlike every other namespace, no redirects
can be made to quickly fix all existing links if a wiki is changed over (as is
the case here).

On a more blue-sky thought: if the idea of database-driven namespaces (I haven't
time to find the reference right now) is taken up in the main code, perhaps
$wgCapitalLinks could become a per-namespace setting. For instance, there's
probably rarely a reason to distinguish between "Project:foo" and "Project:Foo",
even when there is a clear distinction between "Foo" and "foo". But maybe by
then someone will have sorted out a better way of dealing with the whole case
folding issue anyway.
Comment 2 Brion Vibber 2005-07-16 01:29:33 UTC
In phase 2, special page matching was case-insensitive; that got broken in 
the phase 3 code and nobody ever got around to fixing it. The first letter is 
automatically capitalized normally so nobody notices that most common 
case, except where $wgCapitalLinks is off.

(Note that namespace names are also case-insensitive matches; it's only in-
database titles and usernames which are sensitive.)
Comment 3 lɛʁi לערי ריינהארט 2005-11-13 10:24:38 UTC
Dear friends,

Regarding case sensitive topics one coud suggest to handle two namespaces

a) no accounts starting with lowercase letters are alloew in {{:ns:user}}
as a consequence see
bug 3904: disallow user pages and user_talk pages starting with lower case on
case sensitive wikis

b) for {{ns:special}} [[special:foo]] should be equivalent to [[SpECIaL:Foo]].
note: generic namespaces are completely case insensitive

regards reinhardt [[user:gangleri]]
Comment 4 lɛʁi לערי ריינהארט 2005-11-14 02:29:48 UTC
please note that the *error message* capitalizes the first character

*No such special page*

You have requested an invalid special page, a list of valid special pages may be
found at Special:Specialpages.

Return to Main Page
*S*pecialpages with *S*
Comment 5 lɛʁi לערי ריינהארט 2005-11-15 09:10:47 UTC
see also
bug 2874: Special namespace case sensitive when $wgCapitalLinks=false;
Comment 6 lɛʁi לערי ריינהארט 2005-12-22 21:01:17 UTC
(In reply to comment #5)
> see also
> bug 2874: Special namespace case sensitive when $wgCapitalLinks=false;

Ups! This was posted at the wrong place.
Comment 7 lɛʁi לערי ריינהארט 2006-04-26 13:31:08 UTC
*** Bug 5132 has been marked as a duplicate of this bug. ***
Comment 8 Rob Church 2006-04-26 19:23:25 UTC
(In reply to comment #4)
> please note that the *error message* capitalizes the first character

Of course it does. It doesn't require thought to realise the reason for that.
Comment 9 Antoine "hashar" Musso (WMF) 2006-12-11 16:15:37 UTC
Works fine with 1.9alpha r18226 .

Marking bug as fixed.

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