Last modified: 2008-06-06 15:57:20 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 14424 - accountcreator user right not bypassing account creation limit
accountcreator user right not bypassing account creation limit
Product: Wikimedia
Classification: Unclassified
General/Unknown (Other open bugs)
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2008-06-06 01:55 UTC by OverlordQ
Modified: 2008-06-06 15:57 UTC (History)
0 users

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


Description OverlordQ 2008-06-06 01:55:05 UTC
According to the wiki SQL gave me the Account creator right earlier this morning[1].  Since then I've created 8 accounts[8].  However going through [[WP:ACC]] to process some of the requests I get the usual unexpected error: "Visitors to Wikipedia using your IP address have created 6 accounts in the last 24 hours, which is the maximum allowed in this time period. "

Which is strange since like I've mentioned I have created about 13 over the past 24 hours and not six, secondly shouldn't the accountcreator should be bypassing this restriction?


Comment 1 Brion Vibber 2008-06-06 15:57:20 UTC
Fixed in r35970.

A logic error was introduced in r35908, which added the 'noratelimit' user right to replace $wgRateLimitsExcludedGroups while attempting to retain compatibility with the old configuration. The wrong boolean operation was used, requiring _both_ settings to match to take effect.

I've changed the function to behave correctly and be a little clearer and more self-documenting.

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