Last modified: 2007-03-08 22:15:22 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 9223 - Disallow ~~~ in page title (or username)
Disallow ~~~ in page title (or username)
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
All All
: Normal minor (vote)
: ---
Assigned To: Nobody - You can work on this!
http://hopper.uoregon.edu/wiki/index....
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-03-08 03:30 UTC by Silas Snider ([[en:User:Simonfairfax]])
Modified: 2007-03-08 22:15 UTC (History)
0 users

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


Attachments

Description Silas Snider ([[en:User:Simonfairfax]]) 2007-03-08 03:30:30 UTC
When ~~~ is a username, null edits will cause recursive expansion of signatures.
Comment 1 Aryeh Gregor (not reading bugmail, please e-mail directly) 2007-03-08 03:32:54 UTC
More than two consecutive tildes should be banned in page titles altogether.  There will be 
obvious brokenness if that's allowed.
Comment 2 Thomas "Tango" Dalton 2007-03-08 19:04:36 UTC
An alternative would be to not expand ~~~ if it appears in a [[link]].
Comment 3 Aryeh Gregor (not reading bugmail, please e-mail directly) 2007-03-08 19:48:11 UTC
Still pretty fishy.  Consider trying to refer to such a user precisely, you want to type out the 
link every time?
Comment 4 Brion Vibber 2007-03-08 22:15:22 UTC
Fixed in r20274; be sure to run the batch validity checks after the update goes
live to weed out remaining bogus entries.

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


Navigation
Links