Extension talk:FlaggedRevs

Archives

Archive 1 Archive 2 Archive 3

Previous page history was archived for backup purposes at Extension talk:FlaggedRevs/LQT Archive 1 on 2015-07-10.

I tried to dump my wiki into an XML and import it into a fresh installation. But FlaggedRevs weren moved too.

I used mediawiki's onboard maintenance scripts.

How would I fix that...?

Unfortunately the out-of-the-box tools of MediaWiki allow only to export "the lastest stable version", but not "all revisions with their flags". Additionally, the import does not know anything about flags.

I want to protect some pages using `action = stabilize`, but I need to check for their current status (expiray, reason, level, etc.). Is there any way to get these info using API?

Found it: https://www.mediawiki.org/w/index.php?title=Extension:FlaggedRevs&diff=3274706&oldid=3214539

I've set $wgFlaggedRevsExceptions = [ '*' ]; for everyone see the latest edit. But this doesn't work.

I've resolved this. I used $wgFlaggedRevsOverride and I set this to false.

$wgFlaggedRevsOverride = false;

Hi, I've installed FlaggedRevs trying to build a Quality Management System. I need that users see the stable version by default, and write the following line in my LocalSettings.php:

$wgFlaggedRevsOverride = true;

However, the page ...: http://myserver/mediawiki/index.php?title=mypage Is the same as ......: http://myserver/mediawiki/index.php?title=mypage&stable=0

I need the stable=1 by default, how can I achieve this ?

Thanks in advance Alfonso

actually it should be enough to simply set

 $wgDefaultUserOptions['flaggedrevsstable'] = false; 

to true; found in \extensions\FlaggedRevs\FlaggedRevs.php

The bad thing about this solution is, that the users could change this behaviour in their preferences.

In case someone runs into the same problem with MW 1.20 or 1.21.

I set the default user options like described above:

$wgDefaultUserOptions['flaggedrevsstable'] = true; 

It worked, but I got an error when I tried to access the preferences with some users (they had the default settings for FlaggedRevs):

Fatal exception of type MWException 

My solution was to set the default options to this:

$wgDefaultUserOptions['flaggedrevsstable'] = 1;

Maybe there was a change since the above solution was written. Hope this helps. :-)

Apologize if I am reviving the old question but want to check if there is a better way than changing the default user option for this question...

Is this a feature of FlaggedRevs? Is there any way I can disable it? Generally on my wiki if pages aren't edited for a long time it means they don't need to be updated, not that they need to be checked again. I'm not 100% sure things are being marked unchecked but it seems like they are.

It’s certainly not a feature, I don’t face with it on Wikimedia sites (mostly Hungarian Wikipedia). Is your wiki public? If yes, could you cite a specific page which has become unchecked?

It is public, mostly there have been some category pages which I'm pretty sure were checked & later on aren't checked. That said I don't have a page that I'm 100% certain this is happening to so I will reply again if I'm certain.

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.

Maybe look at https://www.mediawiki.org/wiki/Extension:FlaggedRevs/Restricting_unapproved_revisions .

In fact the issue is not "how to not show unstable versions" but how to have stable versions only if a tag has reach a certain level.

For exemple, with only one tag with 3 levels Draft-Verified-Approved : how to tell the extension to consider that "Verified" is not a stable state and thus not shown by default (with $wgFlaggedRevsOverride = true)

Is there any update to this? I have the same question:

3 Levels: Draft - Verified - Approved. Only Approved shall be considered as stable, how to achieve this?

Setting is "status" => array('levels' => 2, 'quality' => 3, 'pristine'=3).

Currently all pages having status "Verified" are considered as "stable".

FlaggedRevs is a powerfull tool, but for users beyond Wikipedia you easy lost the orientation. This starts with the fact that when comparing versions I only come back to the page via the article tab, this goes on with unclear labels and missing design. It's a pity that this great and popular expansion on the surface is still so weak. Can we help to move the issue forward? Is there a roadmap?

Is there any way to do this? If the template/file itself has been reviewed already or was done by someone with Editor permission, I don't need to review the change again on the page where it's transcluded/embedded.

And this message shouldn’t appear in that case, only if a non-trusted user edited a used template or file, and that edit hasn’t been reviewed yet. If it’s not the case, please report the bug on Phabricator.

Hmm I think this might be happening because the files were moved to a commons wiki and then deleted from this wiki (example page - https://lol.gamepedia.com/index.php?title=Afreeca_Freecs&oldid=880962&diff=curand I won't check it so it stays). Is that intended behavior?

I know this problem (though I have never reported it as a bug). To be honest, I think there’s no good solution for this problem – I see three possible options: the current one, where you have to mark each page using images from the central image repository as checked, another one is the ability to mark individual images stored in the central repo as checked, including ones that are never actually used on this wiki, and the third is to not require flagging for images of the central repo, which means that not all content will be checked, and vandals can overwrite images with anything with a lower risk of being reverted before anyone could see it.

Could I just totally disable the "pending changes for included files or templates" notice altogether? I know that's not a good option in general but it would work for my wiki - we have Pending Changes more to protect against well-intentioned but incorrect content page updates and rarely have to deal with vandalism or any template edits at all.

Maybe this can help: https://github.com/wikimedia/mediawiki-extensions-FlaggedRevs/blob/8e9cd5c6672eebda3fcf4f8f881c078487e0d619/FlaggedRevs.php#L208-L220

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'

I have the same problem. Anybody have an idea of what might be happening?

What authentication extension do you use?

My wiki does a lot of realtime data entry, and so when I onboard new staff members for data entry, I want their edits to not go through approval before showing up on the page. But I do want them to show up as unpatrolled in Recent Changes so I can check over them at a later time. Does this extension allow for this, and if so, how can I configure it?

You can set $wgFlaggedRevsOverride = false; . Or just use the default patrol system (the disadvantage of the latter is that it’s accessible from fewer places and stores whether a revision was patrolled only for 30 days, but maybe it’s easier to configure).

The problem with that is that I still want changes from most users to be pending and not show up to regular visitors. There's basically three types of editors I need:

• Trusted editors, whose changes will be autopatrolled and accepted and immediately be live
• Trainee editors, whose changes will immediately be live for live data entry purposes, but will not be autopatrolled so that I can review what they did easily from recent changes
• Visitors who happen to edit the wiki, whose changes are both pending & unpatrolled when they edit

Is there any way to set up a system like this?

I don’t know about such settings. (There may be, though, I only know the default mode, not to speak about other extensions.)