Extension talk:FlaggedRevs

From MediaWiki.org
Jump to: navigation, search
Start a new discussion
First page
First page
Previous page
Previous page
Last page
Last page

Show non-checked page version until review = quality or higher

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?

198.214.211.10720:00, 2 December 2014

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.

198.214.211.10616:51, 9 December 2014
 

MW version

I've been using the FlaggedRevs since MW 1.15 at least (march 2010) The Infobox now mentions MW 1.17+ Why?

Arent (talk)14:31, 9 December 2014

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.

[[kgh]] (talk)15:13, 9 December 2014

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.

Arent (talk)15:37, 9 December 2014

You are writing about existing users. They know that it used to work somehow for an ancient release at some time in the past.

[[kgh]] (talk)15:55, 9 December 2014
 

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).

Nemo16:14, 9 December 2014
 
 
 

Set up different Revs for different NS

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...?

Thank you

Gborgonovo (talk)17:32, 6 November 2014

Is ns1 group a subset of ns2, or vice versa? Does ns1 group edit ns2, and vice versa?

Nemo07:32, 7 November 2014

No, they are completly different and separated ns, and the groups (as well) must have different permissions.

Gborgonovo (talk)08:27, 7 November 2014
 
 

Hide newly created article

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?

Regards Dominik

80.70.182.9810:30, 24 June 2014

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?

78.53.96.1323:25, 23 September 2014
 

No new revision if template is changed...

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)

Heinrich krebs (talk)15:04, 14 August 2014

Any help? Please.

Heinrich krebs (talk)16:44, 11 September 2014

Hi,

have a look at $wgFlaggedRevsHandleIncludes. You can find a detailed description in the FlaggedRevs.config.php file in the extensions root folder.

Osnard (talk)11:29, 16 September 2014

Thank you. I will change the settings there, and hope it'll fix the problem.

Heinrich krebs (talk)17:16, 17 September 2014
 
 
 

Class 'FlaggedRevs' not found

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?

Avshukan (talk)13:12, 16 September 2014

Everyone sees Edit Review widget after installation

Hi,

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..

Any idea?

Edga (talk)10:12, 10 September 2014

The reviewer's widget isn't the little box in the top right corner. Everyone is supposed to be able to see that. The reviewer's widget is the big box all along the top of the page with buttons to accept or reject the revision.

Jackmcbarn (talk)14:17, 10 September 2014
 

User groups resetting after relogin

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'

91.197.189.17412:32, 7 August 2014

How to get list of pages with includes

Hi,

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 ?

Best regards,Ludovic.

Ludovic Strappazon (talk)09:31, 12 June 2014

Setting "Revision displayed on default page view" does not work

Hi,

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;

Best, Koem

93.218.105.20616:39, 20 May 2014

advertise not working

Hi!

when I click on "advertise" this text appears: "Notice: Other reviewers can see that you are reviewing these changes."

but:

  • 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

Koemski (talk)16:18, 15 April 2014

bounce

Koemski (talk)11:54, 12 May 2014

I believe the best way is to report a bug on bugzilla in case nobody has done so in the meantime.

[[kgh]] (talk)12:02, 12 May 2014
 
 

Possibility to disable "review is pending message" for anon users?

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.

212.183.43.4817:05, 5 May 2012

You'd have to use site JavaScript/CSS.

Aaron (talk)23:15, 11 May 2012

This is interesting, can you suggest how, please?

Thank you

Gborgonovo (talk)12:56, 15 April 2014
 
 

Pending changes page style

Is it possible to assign a style to paending changes page? Has it a dedicated class? I cannot find it.

Thank you.

Gborgonovo (talk)12:29, 15 April 2014

Restrict to specific pages

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.

Indolering (talk)00:05, 4 April 2014

You can try setting $wgFlaggedRevsProtection = true and manually adding the pages as an admin.

Aaron (talk)23:12, 7 April 2014
 

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.

88.113.156.1207:25, 8 January 2014

Try changing $wgFlaggedRevsRestrictionLevels.

Aaron (talk)23:12, 25 February 2014
 

Getting $wgFlaggedRevsNamespaces configuration in JavaScript

Hello,

I am looking for a way to get the content of $wgFlaggedRevsNamespaces variable through javascript, to define if a particular namespace is under review or not. I've searched in API help but it seems there is no sush a feature.

Of course, I could :

  1. list namespaces through meta=siteinfo&siprop=namespaces
  2. look for the first page in each namespaces with list=allpages
  3. test the flag status of theses pages through prop=flagged

but wow, this is a bit complicated just to get this poor information.

Does anyone know an easier way to do it?

Thank you.

⇨ Dr Brains ∞ Doléances ∞19:13, 20 January 2014

ReviewAllPages.php reports errors

I cann't review all pages using reviewAllPage.php script. The following messages occur:

yoga:/srv/mediawiki-1.21.1/extensions/FlaggedRevs/maintenance # php ./reviewAllPage.php --conf ../../../LocalSettings.php --username Admin

PHP Notice: Undefined index: * in /srv/www/htdocs/mediawiki-1.21.1-II-instancja/extensions/ConfirmEdit/ConfirmEdit.php on line 206 Reviewer username: Admin First argument must be a Title or WikiPage. Backtrace:

  1. 0 /srv/www/htdocs/mediawiki-1.21.1-II-instancja/extensions/FlaggedRevs/backend/FlaggedRevs.class.php(1022): FlaggedRevs::stableVersionUpdates(Object(Article))
  2. 1 /srv/www/htdocs/mediawiki-1.21.1-II-instancja/extensions/FlaggedRevs/maintenance/reviewPagesInFile.php(94): FlaggedRevs::autoReviewEdit(Object(Article), Object(User), Object(Revision), Array, true)
  3. 2 /srv/www/htdocs/mediawiki-1.21.1-II-instancja/extensions/FlaggedRevs/maintenance/reviewPagesInFile.php(26): ReviewAllPages->autoreview_current(Object(User))
  4. 3 /srv/www/htdocs/mediawiki-1.21.1-II-instancja/maintenance/doMaintenance.php(110): ReviewAllPages->execute()
  5. 4 /srv/www/htdocs/mediawiki-1.21.1-II-instancja/extensions/FlaggedRevs/maintenance/reviewPagesInFile.php(118): require_once('/srv/www/htdocs...')
  6. 5 {main}

Can anybody sugest me what I should correct? Thanks in advance.

31.62.233.7710:10, 28 December 2013

Hide or change "Edit" tab on stable pages

Is possible to hide or change the edit tab in a page with at least one stable revision in a given namespace?

FlaggedRevs is enabled at pt.wikisource in some namespaces. The usage on the main namespace is to keep the text as it is on the source (if the source isn't provided by Extension:ProofreadPage but for some resource without original scans), but keeping the page editable for annotations, new metadata, category changes and related stuff. The edit tab may looks for external users as "I can change the words in this work!" even if the changes don't get approved.

See for example s:pt:O Piolho Viajante/XXXVIII (the JS trick on [Expandir] shows the source info).

This is not a community request/question, only an individual user thinking while doing some edits =)

555 (talk)17:51, 13 December 2013

Use api instead of action=ajax

According to the Ajax manual, `api.php` should be used instead of the obsolete `action=ajax`.

I guess and hope that would also allow people (like me ;)) to use the APIAfterExecute to hook into FlaggedRev's actions.

GolezTrol (talk)19:45, 10 December 2013

new page hide until reviewed

A thread, Thread:Extension talk:FlaggedRevs/new page hide until reviewed, was moved from here to Extension talk:Approved Revs. This move was made by Nemo bis (talk | contribs) on 9 December 2013 at 13:20.
First page
First page
Previous page
Previous page
Last page
Last page