Last modified: 2005-08-24 23:30:15 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 573 - Non existent user rights can be set
Non existent user rights can be set
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
All All
: Normal trivial (vote)
: ---
Assigned To: Nobody - You can work on this!
http://meta.wikimedia.org/wiki/Specia...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2004-09-25 21:01 UTC by Angela
Modified: 2005-08-24 23:30 UTC (History)
0 users

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


Attachments

Description Angela 2004-09-25 21:01:28 UTC
In the steward's version of Special:Makesysop, I can assign a user rights that
do not exist. For example, I made myself a bgwiktionary (by accident - I meant
to make myself a sysop).

Also, if the rights field includes the word "sysop", the user is listed on
special:listadmins as a sysop even if they aren't one. For example, Anthere set
a user as sysopbot on zh instead of bot. This had no effect on the user, but
they showed up in the list of admins. The same happened when I set myself as
"not a sysop" on aa.

Entering something unrecognised in the rights field should give an error, not
allow you to set rights that don't exist.
Comment 1 Brion Vibber 2004-09-25 21:03:43 UTC
The set of rights is theoretically open-ended, but this isn't currently used well.

We probably should open a separate bug on that and mark this one as dependent....
Comment 2 Niklas Laxström 2005-08-24 23:30:15 UTC
Seems like this is fixed already

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


Navigation
Links