Last modified: 2008-01-25 22:46:53 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 12790 - [edit=sysop] and [edit=autoconfirmed] without :move=autoconfirmed or move=sysop not listed in log
[edit=sysop] and [edit=autoconfirmed] without :move=autoconfirmed or move=sys...
Product: MediaWiki
Classification: Unclassified
User blocking (Other open bugs)
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2008-01-25 18:40 UTC by Michael Frey
Modified: 2008-01-25 22:46 UTC (History)
1 user (show)

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


Description Michael Frey 2008-01-25 18:40:30 UTC
When I don't set a move protection (check "Unlock move permissions" and choise move "default"), Mediawiki doesn't make a log entrance when I change the edit protection.

To show that Issue:

The Page is edit sysop, move default and that works, but this current block isn't listed in the log.

That's not critical, because sysops are confirmed users and this setting is unusual, but in a bigger wikis with more sysops can it be important to know how locked when what page.
Comment 1 Huji 2008-01-25 22:46:53 UTC
This happened because when the code depended on the last value of number of changed rows in the database, and this value was zero when move-protection was not used, regardless of whether edit-protection was used or not. This is fixed with r30158.

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