Last modified: 2013-09-12 16:26:22 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 T55556, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 53556 - A single colon (:) as title is handled differently
A single colon (:) as title is handled differently
Status: RESOLVED DUPLICATE of bug 54044
Product: MediaWiki
Classification: Unclassified
Parser (Other open bugs)
1.22.0
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-08-29 19:42 UTC by db [inactive,noenotif]
Modified: 2013-09-12 16:26 UTC (History)
0 users

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


Attachments

Description db [inactive,noenotif] 2013-08-29 19:42:26 UTC
The string ':' is treated differently. It is a valid title in Title.php, but also a bad title at other situation:
* Gives no 'invalid': https://en.wikipedia.org/w/api.php?action=query&titles=:
* {{fullurl::}} gives a '//en.wikipedia.org/wiki/'
* but {{fullurl:>}} as invalid title would not parsed
* [[:]] is not parsed
* You cannot view the page corrosponding to : https://en.wikipedia.org/w/index.php?title=:
* Using api action=edit gives a exception: error;{code=internal_api_error_MWException, info=Exception Caught: Something is trying to edit an article with an empty title};
* A move will give articleexists, because there is strlen < 1 check.
* api action=protect allows the (create) protection of that title

In my opinion Title::secureAndSplit should reject a single colon as title.
Comment 1 db [inactive,noenotif] 2013-09-12 16:26:22 UTC

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

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


Navigation
Links