Last modified: 2007-04-15 12:32:46 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 8573 - Unblock interface w/Special:Ipblocklist won't find block IDs with underscores
Unblock interface w/Special:Ipblocklist won't find block IDs with underscores
Product: MediaWiki
Classification: Unclassified
User blocking (Other open bugs)
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2007-01-10 22:52 UTC by Martin Peeks
Modified: 2007-04-15 12:32 UTC (History)
0 users

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


Description Martin Peeks 2007-01-10 22:53:00 UTC
When entering a username for unblock in Special:Ipblocklist&action=unblock, if
spaces are substituted for underscores (_), an error is given: "Block ID not
found. It may have been unblocked already.". Replacing the _ with spaces
resolves the issue.  This becomes a problem with _ in unblock template links (on
WP), and perhaps at times with manual entry.
Comment 1 Raimond Spekking 2007-04-03 10:20:20 UTC
What template do you mean? Please give us the URL. I have tested with FF
at a local installation with a manual entry. No problems. I assume you have to
use {{urlencode:...}} for the username in the template.
Comment 2 Martin Peeks 2007-04-15 12:32:46 UTC
Yes - it seems to work now both in the template and with manual entry, whereas
when I wrote the bug originally, it didn't work.  Perhaps some other change has
fixed this by coincidence - in any case, problem seems solved :).

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