I saw that these questions. I wanted to write the solution. Open the file
extensions/FlaggedRevs/FlaggedRevs.config.php . Edit form :
$wgFlaggedRevsNamespaces = array( NS_MAIN, NS_USER, NS_PROJECT, NS_FILE, NS_MODULE, NS_TEMPLATE, NS_HELP, NS_CATEGORY );. That's it. Now; Go to the main index with PuTTY. ssh command :
php maintenance/populateImageSha1.php run. After;
php extensions/FlaggedRevs/maintenance/updateStats.php run. That will be all. Easy to come.
I think that function to check the selected article will be usefull. This function schuld returned: pageid, title, reviewed version id (+date, +author), most current version id (+date, +author).
You can check if the article is reviewed with this: - https://fi.wikipedia.org/w/api.php?action=query&prop=info%7Cflagged&titles=Turku
If stable_revid=lastrevid then page is reviewed and it doesn't have pending changes If stable_revid!=lastrevid then page is reviewed and it have pending changes if there is no flagged information then page is unreviewed
However i don't think that you can get information of date + author of old version with single query.
I use AutoWikiBrowser to review and script alot of autoedits within my wiki. I would like to be able to review pages with FlaggedRevs at the same time. Is there any collaboration between the two, or has anyone developed any plugins or modules that would allow the cross functionality?
is there a way that reviewers get an email notification about sites that need to be reviewed?
Or is it "only" possible via watchlists?
My customer's desire is, that the reviewers get one mail a week - containing all the articles that have been created or edited. I don't know if that is possible...
This extension could be very useful to my agency, if I can get the configuration set to meet our requirements. I followed the instructions for restricting unapproved revisions, which almost works for my purposes. I have multiple tags, and my wgFlaggedRevsTags array is set such that each tag requires a level 2 in order to be considered "quality". The behavior I'd like to see is that each tag is controlled by a different reviewer, and only when all reviewers have set level 2, and we have "quality" achieved, is the revised page shown to anonymous users. Instead, what I see is that when any of the tags reaches level 2, putting the page into a "checked" state, the page is then displayed to anonymous users prior to the "quality" state being reached. How might I go about fixing this?
It looks as though there is not an available configuration option that I can set to modify the default behavior from accepting draft revisions (i.e. less than quality) as reviewed/stable. I can work around the need for having each reviewer control different levels on different tags, but I really need the viewable versions for anonymous users to only show once quality or pristine levels are reached. Having pages viewable after they have just been checked, but not yet reached quality will not work for my purposes. Can anyone help suggest what modifications I might try to this extension in order to get what I'm after? Many thanks.
When allowing raw html in a wiki ($wgRawHtml), the FlaggedRevs review interface unfortunately shows the changes to the reviewer. Not only in textual form (the diff) but the actually rendered page.
Can this be disabled?
A new created article is always displayed even if not approved. Is there a way to hide newly created articles as in the extension ApprovedRevs?
Yes, this is a feature I am missing most. We're mostly having issues with spammers that create new pages. Hiding new pages by default would discourage spammers. Can you add this please?
This is possible, though the configuration needed is a bit more on the advanced side. For how to configure it, see the page Extension:FlaggedRevs/Restricting unapproved revisions.
I've been using the FlaggedRevs since MW 1.15 at least (march 2010) The Infobox now mentions MW 1.17+ Why?
Actually nobody should use a MW-version older than MW 1.19 so even 1.17 is an outdadated information. The current code in the repo will not work for versions earlier than MW 1.17 anyway. I believe this website should not advertise the usage of outdated and unsupported software since the docu also caters for potential new users. For them it is not important to know that it used to work somehow for an ancient release at some time in the past.
People 'should not' use pre-1.19 MW version of course, but in the meantime you'll find heaps of older installations. Especially when you already have a tooled-up wiki with heavy extensions and/or old-style skins it is not always that easy to upgrade. MW usually upgrades fine but with SMW and FlaggedRevs and skinning and ... I need to stay at 1.16 that I've been using for years. If the infobox says that FlaggedRevs is only useable from 1.17 (downloadable for 1.19++) it displays incorrect information. Sometimes you are forced by circumstances to do what you ideally wouldn't do.
You are writing about existing users. They know that it used to work somehow for an ancient release at some time in the past.
Arent, the extension infobox always talks of master (or latest stable branch). It's a known deficiency that MediaWiki.org currently is unable to provide a compatibility matrix: only Semantic Bundle and MLEB do such a thing, the other extensions are left to wikiapiary: (which we link).
I would like to set up some permissions for a NS and others for another NS. For example:
- NS1: all users can edit, some can review (ns1-reviewers), and somebody can validate (ns1-validators)
- NS2: normal users can only read, only ns2-editors can edit, ns2-reviewers can review (end edit) in ns2, and ns2-validators can validate (and edit and review)
Is this possible? How...?
Hi! I really don't want to re-approve every page that has a certain template, once I change the template. Is there a way to disable this requirement or auto-approve in these cases (if the page was approved before) ? Heinrich krebs (talk) 15:04, 14 August 2014 (UTC)
have a look at
$wgFlaggedRevsHandleIncludes. You can find a detailed description in the
FlaggedRevs.config.php file in the extensions root folder.
Before item 6.2 of Setup manual tried to run updateStats.php and got error about class 'FlaggedRevs' not found.
Then I did items 7 (Enable FlaggedRevs) and 8 (Update MediaWiki's database schemas) and returned to item 6.2. UpdateStats.php worked succesful!
May be move item 6 (Enable collection of article review statistics) after item 8?
I successfully installed FlaggedRevs extension for my internal wiki. However even if I log-in as user I can see Edit Review widget even though in installation notes it says nobody would see it until relevant permissions are granted. the only line for this extension in localsettings I have is require_once..
When I add user to group editor or reviewer or autoreviewer or all off them user can review, all works well. But after user relogin he is deleting from this groups: MessageCache::load: Loading ru... got from global cache Unstubbing $wgParser on call of $wgParser::firstCallInit from MessageCache::getParser Parser: using preprocessor: Preprocessor_DOM Unstubbing $wgLang on call of $wgLang::_unstub from ParserOptions::__construct User: cache miss for user 97 User: loading options for user 97 from database. DatabaseBase::query: Writes done: DELETE FROM `user_groups` WHERE ug_user = '97' AND ug_group = 'editor'
When reading an article with includes, I'm notified by FlaggeRevs about the changes in includes, and it correctly shows the last valid version. But I can't find a way to get a list of pages which includes have been changed.
I have $wgFlaggedRevsAutoReview = FR_AUTOREVIEW_NONE; and $wgFlaggedRevsHandleIncludes = FR_INCLUDES_STABLE; in my Localsettings.php.
Is there a way to get such a list, as we can have the list of reviewed pages with pending changes ?
I use FlaggedRevs REL1_22
Setting the above mentioned option does not have any effect at all. When I set it to "the stable version" I still get the "Pending changes" Tab displayed.
In my personal prefs I set "Use the default settings for each page" and this is my config in LocalPreferences.php:
# Extension:FlaggedRevs $wgFlaggedRevsStatsAge = false; require_once("$IP/extensions/FlaggedRevs/FlaggedRevs.php"); $wgGroupPermissions['sysop']['autoreview'] = false; $wgGroupPermissions['editor']['autoreview'] = false; $wgGroupPermissions['bot']['autoreview'] = false; $wgGroupPermissions['reviewer']['autoreview'] = false; $wgFlaggedRevsTags = array( 'accuracy' => array( 'levels' => 1, 'quality' => 1, 'pristine' => 1 ), ); $wgFlaggedRevsAutoReview = false;
when I click on "advertise" this text appears: "Notice: Other reviewers can see that you are reviewing these changes."
- for other users this changes nothing. Another reviewer doesn't see that I'm reviewing that page
- when I click on "de-avertise" nothing happens. The text doesn't disappear.
Version: REL1_22 with mw1.22.5
Currently on edited pages a message "N changes in this version are pending review. ..." shows up. While this is certainly interesting for users that may edit, especially reviewers, I don't want this information to display for anon users at all. Same question for the small dropdown with the same info on the right. Thanks.
I only need this on a few pages. I know there is a whitelist, but I need ALL of my pages except a few exempted. Is there a way to create an array of the titles of all current pages and then remove the specific pages? Could I create a specific category? I know I can restrict it to a namespace, but these are just basic articles + the main page.
How do I modify the protection interface for stable settings (add more than just none and sysop)?
Right now I have $wgFlaggedRevsProtection=true and when I go to protect the page, it shows the flaggedrevs settings all right but the only options are to not protect it (allow all) and protect it so that it must be reviewed AND auto-reviewed by sysop. I want it to be possible for autoconfirmed to auto-accept their own edits like on enwiki with pending changes protection enabled. I have let "autoconfirmed" to have "autoreview" but still those two (none and sysop) are the only protection settings in the menu.