Extension:FlaggedRevs

Article validation allows for a reviewer class of users to rate article's accuracy/depth/style and set those revisions as the default revision to show upon normal page view (".../wiki/pagename").

These revisions will remain the same even if included templates are changed or images are overwritten. The text with expanded transclusions is stored. Image revisions that were deleted/moved will not however. Depending on the configuration, this may not be a limitation for transcluded pages as well.

Status
The extension is still in heavy early development, but enough code is there to play arround with it. Everything can and will change though ;-)

There is an instance running here, and notes about your finding can be left on the FlaggedRevsNotes page.

Setup
Add the  line to localsettings.php.

Run the FlaggedRevs.sql query, substituting in your wiki's table prefix.

As the relevant core changes have not yet been made to svn trunk, to test this, you must:


 * Run the following SQL query:
 * Apply the patch for bug 5877. This will be on /trunk eventually, but is not yet.
 * Preferably, when rebuildImages.php is updated, run the maintenance script, though its not required.

Configuration
FlaggedRevs.php comes with a number of configurable variables. To modify these, it is best if you copy them to localsettings.php and change them there.

Use
First, make sure there is a bureaucrat or steward account (Stewards can set any arbitrary rights). Bureaucrat accounts, by default, can promote users to reviewer status or remove it.

Users with reviewer status will have a small rating form on page view and diffs that lets them review revisions.

Logging
A log of promotion/demotion of reviewers and why is kept at Special:Log.

A log of the approval/unapproval of revisions is kept at Special:Log.

Issues
Cache - not yet resolved. The imagelinks and pagelinks tables let MW know which pages to purge when a page is moved/deleted/created. However, the stable version links may not be the same as those on the current page, causing it to possibly have red/blue links that should be blue/red. Pressing the "purge" tab ('&action=purge') will reset both the current and stable version cache though.

History merges - If two pages are merged that were around during the same time period, the interwoved history may cause FlaggedRevs to transclude the wrong page version onto the stable version.

Dependencies

 * bug 5877
 * FileStore - this extension will be delayed until some work here is done, so as to avoid conflicts
 * Bitfields for rev_deleted - for preserving page histories

Licensing and downloads
(c) GPL, Jeorg Baach, Aaron Schulz, 2007