Last modified: 2008-01-25 22:46:53 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T14790, the corresponding Phabricator task for complete and up-to-date bug report information.
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...
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
User blocking (Other open bugs)
1.12.x
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  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: ---


Attachments

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:
http://de.wikibooks.org/wiki/Benutzer:MichaelFrey/_Spielwiese
http://de.wikibooks.org/w/index.php?title=Spezial%3ALogbuch&type=protect&user=&page=Benutzer%3AMichaelFrey%2F+Spielwiese

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.


Navigation
Links