Last modified: 2011-03-13 18:05:35 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 14250 - Template changes get autoflagged after a revert is autoflagged
Template changes get autoflagged after a revert is autoflagged
Product: MediaWiki extensions
Classification: Unclassified
FlaggedRevs (Other open bugs)
All All
: Lowest minor (vote)
: ---
Assigned To: Aaron Schulz
Depends on:
  Show dependency treegraph
Reported: 2008-05-24 19:42 UTC by Church of emacs
Modified: 2011-03-13 18:05 UTC (History)
0 users

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


Description Church of emacs 2008-05-24 19:42:45 UTC
This bug seems to be a result of the fix of Bug 13978 (Reverting to a flagged revision should automatically mark the resulting revision as flagged, too).

In the following situation, changes to templates get autoflagged without anyone checking them:
1. article with latest flagged version exist, but it has a template that needs to be flagged
2. Vandal does nasty edit
3. Edit gets reverted and revert edit autoflagged because article was flagged at 1.

A picture is worth a thousand words:

I propose not to pay too much attention to this bug; a real management of flaggedrevs on templates is needed (imho). This bug report is just for your information.
Comment 1 Aaron Schulz 2008-05-25 03:22:52 UTC
This was discussed a lot in the mailing list. It is not likely to matter, and the template/image review solution will be enabled shortly (I've just been testing and improve it recently, the code is old).

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