Erweiterung:Flagged Revisions

Warnung:

Flagged Revisions is very challenging to deploy and maintain, and can have seriously adverse effects on your wiki. Use with caution.

Um zu lernen, wie man Flagged Revisions verwendet, lies die Hilfeseite über Flagged Revisions. (protection-based config )

MediaWiki-Erweiterungen

Flagged Revisions Erscheinungsstatus: stabil
Einbindung	User interface, Special page , Benutzerrechte , Datenbank , Ajax, API
Beschreibung	Flagged Revisions lässt Artikelinhaltsverwaltung für "Bearbeiter" und "Sichter"-Klassen zu.
Autor(en)	Aaron Schulz, Joerg Baach
Kompatibilitätspolitik	Release-Zweige
MediaWiki	1.21+
Datenbankänderungen	Ja
Tabellen	flaggedpages flaggedpage_pending flaggedrevs flaggedtemplates flaggedimages flaggedpage_config flaggedrevs_tracking flaggedrevs_promote flaggedrevs_statisticsn
Lizenz	GNU General Public License 2.0 or later
Herunterladen	Download snapshot Git [?]: Git master herunterladen Repository durchsuchen (GitHub) commit history Code-Review
Hinzugefügte Rechte review, autoreview, autoreviewrestore, validate, stablesettings, movestable
Verwendete Hooks APIGetAllowedParams APIQueryAfterExecute ArticleDeleteComplete ArticleEditUpdates ArticleMergeComplete ArticleRevisionUndeleted ArticleRevisionVisibilitySet ArticleRollbackComplete ArticleUndelete ArticleUpdateBeforeRedirect ArticleViewHeader AutopromoteCondition BeforePageDisplay BeforeParserFetchFileAndTitle CategoryPageView ChangesListInsertArticleLink ChangesListSpecialPageQuery ChangesListSpecialPageStructuredFilters ContribsPager::getQueryInfo ContributionsLineEnding DeleteAccount DiffViewHeader EchoGetDefaultNotifiedUsers EditPage::showEditForm:fields EditPage::showEditForm:initial EditPageBeforeEditButtons EditPageGetCheckboxesDefinition EditPageNoSuchSection FileUpload GetPreferences getUserPermissionsErrors GoogleNewsSitemap::Query ImagePageFileHistoryLine ImagePageFindFile InitializeArticleMaybeRedirect LoadExtensionSchemaUpdates LocalFile::getHistory MagicWordwgVariableIDs MakeGlobalVariablesScript MergeAccountFromTo NewDifferenceEngine NewRevisionFromEditComplete PageContentSaveComplete PageHistoryBeforeList PageHistoryLineEnding PageHistoryPager::getQueryInfo ParserFirstCallInit ParserGetVariableValueSwitch ParserTestTables ProtectionForm::buildForm ProtectionForm::save ProtectionForm::showLogExtract RecentChange_save ScribuntoExternalLibraries SkinAfterContent SkinTemplateNavigation SkinTemplateTabs SpecialNewpagesConditions SpecialNewPagesFilters SpecialPage_initList TitleGetEditNotices TitleMoveComplete UserGetRights UserLoadAfterLoadFromSession UserMergeAccountFields WikiExporter::dumpStableQuery
Bereitgestellte Hooks FlaggedRevsFRGenericSubmitFormReady NewRevisionFromEditComplete FlaggedRevsRevisionReviewFormAfterDoSubmit
Übersetze die FlaggedRevs Erweiterung
Prüfe die Benutzungs- und Versionsmatrix.
Probleme	Offene Aufgaben · Einen Fehler melden

Die Erweiterung Flagged Revisions, zu deutsch auch "Markierte Versionen", ermöglicht es Benutzern der Gruppe Editor (also Bearbeiter) und Reviewer (also Sichter), Versionen von Artikeln zu bewerten und diese Versionen als Standardversion auf eine normale Ansicht zu setzen. Diese Versionen werden die gleichen bleiben, auch wenn eingebundene Vorlagen oder Bilder geändert werden. Dies ermöglicht MediaWiki, sich mehr wie ein Content Management System zu verhalten.

Download

Die Erweiterung kann man direkt von Git erhalten ^[?]:

• Den Code ansehen
• Einige Erweiterungen haben Hinweise für stabile Releases.
  • Hinweise ansehen
  • Entsprechend auswählen
  • Klick „snapshot“
• Jeder Zweig ist mit einem vergangenen MediaWiki Release assoziiert. Es gibt außerdem einen „Master“-Zweig, der die aktuellste Alpha-Version enthält (dies könnte eine Alpha von MediaWiki erfordern).
  • Zweige ansehen
  • Einen Zweignamen auswählen
  • Klicke „Continue“

Extrahiere den Snapshot und kopiere ihn in das extensions/FlaggedRevs/de/-Verzeichnis der MediaWiki-Installation.

Falls man sich mit git auskennt und einen Konsolen-Zugang zum Server hat, kann man die Erweiterung auch so bekommen:

cd extensions/
git clone https://gerrit.wikimedia.org/r/mediawiki/extensions/FlaggedRevs%2Fde.git

Einrichtung

Die Beispiele in dieser Installationsanleitung sind für moderne Unix-ähnliche Betriebssysteme (speziell Linux und Mac OS X) geschrieben und setzen voraus, dass MediaWiki in dem Ordner /var/www/mediawiki installiert ist. Wenn du auf einer anderen Familie von Betriebssystemen arbeitest, wirst du Befehle und Dateipfade entsprechend dem Betriebssystem gebrauchen müssen.

Befolge diese Schritte, um FlaggedRevs zu installieren:

1. Stelle sicher, dass du MediaWiki Version 1.17 oder höher verwendest. Falls nicht, musst du upgraden, bevor du FlaggedRevs installieren kannst.
2. Lade FlaggedRevs herunter. Wähle eine Version von FlaggedRevs, die mit der verwendeten Version von MediaWiki übereinstimmt. Wenn du z. B. MediaWiki 1.17 verwendest, lade FaggedRevs 1.17 herunter.

Entpacke die heruntergeladene Datei in das Verzeichnis 'extensions/FlaggedRevs' Deiner MediaWiki-Installation. Zum Beispiel:

1. tar -xzf FlaggedRevs-MW1.17-r75373.tar.gz -C /var/www/mediawiki/extensions

2. Stelle sicher, dass die Bild-Hashes aktuell sind, indem Du das Wartungs-Skript populateImageSha1.php ausführst. Zum Beispiel:

   php maintenance/populateImageSha1.php

Stelle sicher, dass das Verzeichnis extensions/FlaggedRevs/frontend/modules vom Webserver gelesen werden kann (damit der Webserver CSS-, Bild- und JavaScript-Dateien von FlaggedRevs ausliefern kann.) Zum Beispiel: Für den Fall, dass der Webserver die Besitzrechte am Verzeichnis extensions/FlaggedRevs/frontend/modules nicht besitzt, führe folgenden Befehl aus:

1. chmod o+r extensions/FlaggedRevs/frontend/modules

2. Erlaube das Sammeln von Statistiken über das Sichten von Artikeln.
   1. Deaktiviere das Erstellen von Statistiken bei Bedarf. Setze $wgFlaggedRevsStatsAge = false; in LocalSettings.php . Dies verhindert die Erzeugung von Statistiken, wenn auf Artikel zugegriffen wird (was zu schlechter Performance führen könnte, wenn auf viele Artikel ohne aktuelle Statistik gleichzeitig zugegriffen würde).
   2. Konfiguration der zeitplangesteuerten Erstellung von Statistiken. Erstelle einen cron-Job, der extensions/FlaggedRevs/maintenance/updateStats.php in einem regelmäßigen Intervall ausführt. Führe time php updateStats.php aus um herauszufinden, wie lange die Skriptausführung dauert und stelle das Intervall des cronjobs entsprechend ein. Um beispielsweise einen cronjob zu erstellen, der updateStats.php als Benutzer www-data jede Stunde ausführt:

      echo "@hourly php /var/www/mediawiki/extensions/FlaggedRevs/maintenance/updateStats.php" | crontab -u www-data -

Warnung:

This will delete all existing cron jobs for the user.

1. Aktiviere FlaggedRevs durch hinzufügen der folgenden Zeile in LocalSettings.php :

   require_once("$IP/extensions/FlaggedRevs/FlaggedRevs.php");
   

2. Aktualisiere die Datenbank-Strukturen durch Ausführen von php maintenance/update.php. Dies muss ausgeführt werden nachdem der obige Schritt gespeichert wurde. Andernfalls wirst Du einen Datenbankfehler beim Zugriff auf jede Seite erhalten.
3. Weise Benutzern Sichter-Rechte zu. Nach der Erstinstallation von FlaggedRevs ist das Sichter-Widget zunächst bei keinem Benutzer angezeigt. Um dies zu ändern, melde Dich als Wiki-Bürokrat an und öffne Special:UserRights und erteile Sichter-Rechte an einen oder mehrere Benutzer. Sichter werden nun das Sichter-Widget am Ende einer editierbaren Seite sehen.

Wikimedia-Serverinstallation

Siehe auch wikitech:Heterogeneous deployment#Install a new extension on a wiki und wikitech:How to do a schema change.

Instructions for Wikimedia projects community: m:Flagged Revisions#Enabling.

Diese Notizen sind spezifisch für die Wikimedia-Server und sind wahrscheinlich nicht auf Ihr Setup anwendbar.

cd /a/common/php-1.23wmf5
mwscript sql.php --wiki=metawiki extensions/FlaggedRevs/backend/schema/mysql/FlaggedRevs.sql
cd ..
sync-dir wmf-config
touch wmf-config/InitialiseSettings.php
sync-common-file flaggedrevs.dblist
sync-dir wmf-config

Konfiguration

Benutzerrechte und Benutzergruppen

Standardmäßig kann niemand etwas überprüfen. Der erste Schritt ist es also Benutzerrechte einzurichten.

Benutzergruppen	Benutzerrechte
reviewer	validate
	review
editor
	autoreview
	unreviewedpages

Benutzerrechte

FlaggedRevs creates the following new user rights:

• review – user can review revisions
• validate – user can review revisions and can set all tags to all levels
• autoreview – any new revisions made by the user are automatically marked as sighted
• autoreviewrestore – autoreview of the rollbacks made by the user.
• unreviewedpages – user can view Special:UnreviewedPages
• stablesettings – user can changes the settings of stable revisions of any page
• movestable – user can move pages with stable revisions

Benutzergruppen

FlaggedRevs creates the following new user groups:

• editor – receive autoreview, review, unreviewedpages, plus the standard MediaWiki user rights autoconfirmed, editsemiprotected
• reviewer – receive autoreview, review, unreviewedpages, validate, plus the standard MediaWiki user rights autoconfirmed, editsemiprotected
• autoreview – receive autoreview

Benutzerrechte zuweisen

User rights can be assigned in two ways:

• Assigning rights to user groups
  Assign these user rights to existing user groups in LocalSettings.php :

$wgGroupPermissions['sysop']['review'] = true; //allow administrators to review revisions

• Assigning rights to specific users
  Manually add user accounts to the appropriate groups via Special:UserRights.

By default:

• Bureaucrats can add/remove Reviewers
• Administrators can add/remove both Autoreviewers and Editors.

Grundeinstellungen

FlaggedRevs.php comes with a number of configurable variables. These should be configured in LocalSettings.php.

• $wgFlaggedRevsNamespaces – Sets what namespaces may be subject to the review process. This is an array of integers. Look at the beginning of includes/Defines.php to see what integer the default namespaces map to and use the defined constants for readability.
• $wgFlaggedRevsTags – Sets the tags and their three settings: 'levels', 'quality', and 'pristine'

  Definition

  $wgFlaggedRevsTags is an associative array with keys corresponding to each tag name and values that are arrays of the three settings 'levels', 'quality', and 'pristine':

  • 'levels' controls the number of review levels,
  • 'quality' decides what level the tag must be for a revision to be 'quality'
  • 'pristine' decides what level the tag must be for a revision to be 'pristine'

  Labeling

  • Each tag can be labeled editing the page MediaWiki:revreview-<tag-name>.
  • Each tag level can be labeled editing the page MediaWiki:revreview-<tag-name>-<level-number>.

  Beispiel

  Suppose one wants to have "accuracy", "depth", and "tone" tags, with 3 levels each.

  The admins also want revisions with at least "accuracy" and "depth" of the 2nd levels to count as "quality". The following settings will do that:

  $wgFlaggedRevsTags = [
  	'accuracy' => [ 'levels' => 3, 'quality' => 2, 'pristine' => 4 ],
  	'depth'    => [ 'levels' => 3, 'quality' => 2, 'pristine' => 4 ],
  	'tone'     => [ 'levels' => 3, 'quality' => 1, 'pristine' => 4 ],
  ];
  

  By default, the tags are labeled as they are set in the $wgFlaggedRevsTags array. In this example this means the tags appear exactly as 'accuracy', 'depth' and 'tone'.

  To show tags for example as their capitalized name, the admins have to edit these pages with the shown content:

Tag	labeling page	Inhalt
accuracy	MediaWiki:revreview-accuracy	Status
depth	MediaWiki:revreview-depth	Tiefe
tone	MediaWiki:revreview-tone	Tone

To label the tag levels, the admins have to create these pages with the shown content:

Tag	level	labeling page	Inhalt
accuracy	0	MediaWiki:revreview-accuracy-0	unzureichend
	1	MediaWiki:revreview-accuracy-1	Überprüft
	2	MediaWiki:revreview-accuracy-2	geprüft
depth	0	MediaWiki:revreview-depth-0	Unzureichend
	1	MediaWiki:revreview-depth-1	einfach
	2	MediaWiki:revreview-depth-2	mittel
tone	0	MediaWiki:revreview-tone-0	Woche
	1	MediaWiki:revreview-tone-1	Gut
	2	MediaWiki:revreview-tone-2	Exzellent

The resulting setup will be:

Tag-Namen	level names
Status	unzureichend	Überprüft	geprüft
Tiefe	Unzureichend	einfach	mittel
Tone	Woche	Gut	Exzellent

• $wgFlaggedRevsOverride – Whether the stable version is the default content for pages.

  Individual pages can be configured to have the stable or draft version as the default content by administrators.

• $wgFlaggedRevsTagsRestrictions – An array with keys corresponding to each flag type, and values that are arrays of rights and how high users with it can rate the flags (integral tag level).

  Beispiel

  $wgFlaggedRevsTagsRestrictions = [
  	'accuracy' => [ 'review' => 1 ],
  	'depth'	   => [ 'review' => 2 ],
  	'style'	   => [ 'review' => 3 ],
  ];
  

• $wgFlaggedRevsWhitelist – Array of string titles. These titles are pages that are exempt from FlaggedRevs. They are unreviewable and have no flagging UI. Replace ' ' with '_' in titles (e.g. "Main page" -> "Main_page").

Benutzeroberfläche

• $wgSimpleFlaggedRevsUI – When enabled, a simpler, icon based UI is used. Does not affect the tags shown in edit mode.
• $wgFlaggedRevsLowProfile – This setting hides the review status box/bar for pages that are reviewed in their latest version. Explanatory text is also removed from some places.

Ablauf

• $wgFlaggedRevsExceptions – Makes users in these groups see the current/draft revision by default.
• $wgFlaggedRevsAutoReview – If enabled, every edit by a user with 'autoreview' rights is automatically reviewed upon save. There is no need to hit the "submit review" button. This feature requires that the previous revision was also reviewed; otherwise, auto-review will not occur.
• $wgFlaggedRevsTagsAuto – If wgFlaggedRevsAutoReview is enabled, this settings controls how high each tag can be auto-reviewed. If allowed, tags will be auto-reviewed to the same level the previous revision tags were. This is an associative array; each key is a tag and each value is a tag level.

  Beispiel

  $wgFlaggedRevsTagsAuto = [
  	'accuracy' => 1, 'depth' => 1, 'style' => 1
  ];
  

Changes in templates and images are auto-reviewed (per-page). This could possibly cause bad versions to be reviewed. Users should be encouraged to use preview or review the page after saving. You may want to set $wgNamespaceProtection[NS_IMAGE] and $wgNamespaceProtection[NS_TEMPLATE] as [ 'editor' ] or [ 'autoconfirmed' ]

Automatische Benutzerbeförderung

• $wgFlaggedRevsAutopromote – An array with keys for days, edits, time spacing, benchmarks, emailconfirmed, recent content page edits, total content edits, content pages edited, edit summaries used, IP uniqueness, and userpage existence as keys. The values correspond to how many days/edits are needed for a user account to be autopromoted to Editor status and whether they must be emailconfirmed and have a user page do so. The user must have at least X edits that are Y or more days apart, where X is the number of benchmarks and Y is the time spacing. Set this variable to false to disable this entirely.
  • If a user has their Editor rights removed, they will not automatically be re-granted (the editor status log is checked for revocations).
  • Some of these counts are not retroactive, so you may notice a delay in promotions.

  Beispiel

  For $wgFlaggedRevsAutopromote, one might have:

  $wgFlaggedRevsAutopromote['days'] = 60; # days since registration
  $wgFlaggedRevsAutopromote['edits'] = 150; # total edit count
  $wgFlaggedRevsAutopromote['excludeDeleted'] = true; # exclude deleted edits from 'edits' count above?
  $wgFlaggedRevsAutopromote['spacing'] = 3; # spacing of edit intervals
  $wgFlaggedRevsAutopromote['benchmarks'] = 15; # how many edit intervals are needed?
  $wgFlaggedRevsAutopromote['recentContentEdits'] = 10; # $wgContentNamespaces edits in recent changes
  $wgFlaggedRevsAutopromote['totalContentEdits'] = 30; # $wgContentNamespaces edits
  $wgFlaggedRevsAutopromote['uniqueContentPages'] = 10; # $wgContentNamespaces unique pages edited
  $wgFlaggedRevsAutopromote['editComments'] = 5; # how many edit comments used?
  $wgFlaggedRevsAutopromote['email'] = true; # user must be emailconfirmed?
  $wgFlaggedRevsAutopromote['userpageBytes'] = 0; # if userpage is needed, what is the min size?
  

Erweitert

See FlaggedRevs.php for a complete list of configuration options (with some explanatory comments). Be sure to change only localsettings.php to set configuration options rather than editing this file.

To have a wiki where non-users can only see the stable version of articles, see Extension:FlaggedRevs/Restricting unapproved revisions .

Verwendung

Siehe auch: Help:FlaggedRevs

Seiten genehmigen

Users with some level of review status will have a small rating form on page view (at the bottom of the page) and diffs (at the top of the page) that lets them review revisions. Each tag must at least meet the minimal level of approval. Users should look at the whole page, included templates and images, before reviewing. The (diff to stable) link is very useful for speeding up this process.

Users cannot review a page which they cannot edit. They cannot lower the level of a revision from a level they cannot set. Blocked users cannot do anything.

At Special:StableVersions, you can list out all of the reviewed revisions for a certain page or view reviewed revisions.

Pflege

At Special:UnreviewedPages, there is a list of pages that have not yet been reviewed, for Editors only. A namespace must be selected and an optional category filter is also present.

At Special:OldReviewedPages, there is a list of pages that have been reviewed, but have edits pending. This is for Editors only. An optional category filter is also present.

Pages that cannot be reviewed can still be patrolled for anti-vandalism purposes by Editors to see what has been checked already.

A list of reviewed pages at the main review levels can be found at Special:ReviewedPages.

Protokollierung

All relevant actions are permanently logged, so everything can be tracked and overseen properly.

• A log of promotion/demotion of editors and the reasons is kept at Special:Log/userrights.
• A log of the approval/unapproval of revisions is kept at Special:Log/review.
• A log of changes to the stable versioning configuration to pages is logged at Special:Log/stable.

Also, a new page, Special:QualityOversight shows only flaggings log entries related to quality revisions. This is useful if the main log is too flooded with page "sightings".

Hinweise

• $wgUseRCPatrol is enabled with the extension. Patrolling of reviewable pages is disabled, but flagged revisions are marked as patrolled in Recent Changes. This will mean that the only way to patrol a reviewable revision is to flag it. Non-reviewable pages still behave as normal (depending on site patrol settings).
• Sysops can change whether quality revision have precedence or whether the stable version is shown by default for specific pages. To disable this, add $wgGroupPermissions['sysop']['stablesettings'] = false; to LocalSettings.php.
• Page links, category, image, template, language, and external links are still based on the current version of pages.
• Users cannot move pages they cannot review. This is deliberate; see phab:T15994. To work around this, add $wgGroupPermissions['autoconfirmed']['movestable'] = true; to LocalSettings.php
• You can demote Editors either temporarily by blocking them or permanently via Special:UserRights. An extra demotion log item will appear for tracking purposes.

API

FlaggedRevs adds API modules for reviewing revisions and configuring "stabilization" of pages, a module for retrieving flag configuration, and three list modules corresponding to the special pages for reviewed pages, unreviewed pages and "old" reviewed pages.

Some more API documenation is at Extension:FlaggedRevs/API.

action = review

Main page: API:Review

Reviews a page.

Parameter

• revid: The revision ID for which to set the flags
• token: A csrf token retrieved through action=query&meta=tokens
• comment: Comment for the review (optional)
• flag_accuracy: Set the flag named "accuracy" to the specified value; (replace "accuracy" with the flag name to set another flag)

Beispiel

Review revision 12345

api.php?action=review&revid=12345&token=123ABC&flag_accuracy=1&comment=OK [try in ApiSandbox]

action = stabilize

Changes page stabilization settings.

Parameter

• title: Title of page to be stabilized
• reason: Reason for stabilization
• expiry: (Deprecated?) Stabilization expiry. Default: infinite
• review: Whether to auto-review the page
• watch: Whether to watch the page
• token: An edit token retrieved through prop=info
• For protection-like configurations ($wgFlaggedRevsProtection=true):

  protectlevel: The right users must have in order for their edits to not require review.

• Otherwise ($wgFlaggedRevsProtection=false):

  default: Default revision to show (latest | stable)

  precedence: Which stable revision should be shown (pristine | quality | latest). Default: quality

  autoreview: Restriction level for the 'autoreview' right (sysop | none). Default: none

Beispiel

Configure the page "Foo" such that only quality revisions are shown by default

api.php?action=stabilize&title=Foo&reason=Because_I_can&precedence=quality&default=stable&token=abc123 [try in ApiSandbox]

action = flagconfig

Shows information about review flag configuration.

The following parameters are returned for each tag:

• name: the name of the flag
• levels: the number of possible levels the flag has (not counting the "unreviewed" level)
• tier2: level the flag must be for the revision to be considered "quality"
• tier3: level the flag must be for the revision to be considered "pristine"

The displayed name for each flag and the different level names for each flag are MediaWiki messages, so can be set and retrieved through the appropriate page; for example the name for the first level of the "accuracy" flag is located at MediaWiki:revreview-accuracy-1.

Beispiel

Retrieve flag configuration

api.php?action=flagconfig [try in ApiSandbox]

list = reviewedpages

Lists pages that have been reviewed.

Parameter

• rpstart: Start listing at this page id.
• rpend: Stop listing at this page id.
• rpdir: In which direction to list.
• rpnamespace: The namespaces to enumerate.
• rpfilterredir: How to filter for redirects
• rpfilterlevel: How to filter by quality (0=sighted,1=quality)
• rplimit: How many total pages to return.

Beispiel

List "sighted" pages in main namespace

api.php?action=query&list=reviewedpages&rpnamespace=0&rpfilterlevel=0 [try in ApiSandbox]

list = unreviewedpages

Lists pages which have never been reviewed.

Parameter

• urstart: Start listing at this page title.
• urend: Stop listing at this page title.
• urnamespace: The namespaces to enumerate.
• urfilterredir: How to filter for redirects
• urfilterlevel: How to filter by quality (0=sighted,1=quality)
• urlimit: How many total pages to return.

Beispiel

List pages in the main namespace that have not been "sighted"

api.php?action=query&list=unreviewedpages&urnamespace=0&urfilterlevel=0 [try in ApiSandbox]

list = oldreviewedpages

Lists pages that have at some point been reviewed, but for which the most recent revision is not reviewed.

Parameter

• orstart: Start listing from this timestamp
• orend: Stop listing at this timestamp.
• ordir: In which direction to list.
• ornamespace: The namespaces to enumerate.
• orfilterredir: How to filter for redirects
• orlimit: How many total pages to return.

Beispiel

List pages in the main namespace with recent unreviewed revisions

api.php?action=query&list=oldreviewedpages&ornamespace=0 [try in ApiSandbox]

prop=flagged

Use action=query&prop=flagged to get information about the flagging status of the given pages.

Begrenzungen

• Transclusions across wikis are not stabilized
• External images (aside from Commons) are not stabilized
• Metatemplates that conditionally include other templates may have the condition change between the time a reviewer loaded a page and when they reviewed it. Therefore, there would be no pointers to the revision id for this different template to load from, making it blue linked. You will be notified if this happens during review.

Deinstallieren

1. Remove the include line from LocalSettings.php
2. Drop the tables in FlaggedRevs.sql.
3. Drop the columns page_ext_reviewed, page_ext_quality, and page_ext_stable, and the index ext_namespace_reviewed from the page table (if they exist; only older versions of FlaggedRevs used these)
4. Run maintenance/refreshLinks.php from the command line to flush out the stable version links
5. Run maintenance/rebuildFileCache.php 0 overwrite from the command line if you use $wgFileCache

Testplattformen

• Englisch
• Deutsch
• Polnisch

Siehe auch

• Hilfe:Überprüfte Bearbeitungen
• Extension:FlaggedRevs/Specifications
• Extension:Approved Revs
• Extension:Moderation – edits remain private until they're approved
• meta:Flagged Revisions#Flagged Revisions on Wikimedia projects
• Project:Editor – documentation about the user groups and rights created by this extension, while it was at use on mediawiki.org

Weblinks

• Quality Assurance in an Open Project – 2008 Wikimedia blog post
• Images of Flagged Revisions – Wikimedia Commons
• Über Flagged Revisions – Meta-Wiki

Lizenzierung

© GPL, Aaron Schulz, Joerg Baach, 2007