Extension talk:FlaggedRevs

Jump to: navigation, search

About this board

Archives 


By clicking "Add topic", you agree to our Terms of Use and agree to irrevocably release your text under the CC BY-SA 3.0 License and GFDL
31.172.189.50 (talkcontribs)

In my wiki when user without high permissions create a new page this page is unreviewed so next edits aren't reviewed. Is it possible to set up that every new page create by user automatically has stable version?

Tacsipacsi (talkcontribs)

Why would it be good? The goal of FlaggedRevs is to have all edits manually flagged—it includes page creations. (Of course it doesn’t refer to “high permissions”, i.e. at least autoconfirmed users, whose edits to flagged pages are always flagged—again regardless of whether it’s a page creation or a normal edit.)

31.172.189.50 (talkcontribs)

You are right but when user without autoconfirmed perimissions created a new page and wrote content, reviewer can't reject this revision only accept. So it is possible to set up that first automatically stable version of new page is blank page and all content which user wrote will be pending changes?

Tacsipacsi (talkcontribs)

We use this extension on the Hungarian Wikipedia, and the general rule is that a reviewer should flag the revision (while reverting or tagging it if not correct). The technical equivalent of reverting at new pages is speedy deletion (for non-sysops it’s of course marking for speedy, while flagging it). Why would be the stable version a never-existed one?

P.gibellini (talkcontribs)

Is there a way to hide the new pages until they aren't revised?

Tacsipacsi (talkcontribs)

Currently there isn't. How do you think it (i.e. what would anonymous users see instead of the article; what would be the color of links pointing to such articles, red or blue)? Or what do you mean under "hiding" of these articles?

P.gibellini (talkcontribs)

This is a good question. A new page created by a normal user at the moment is immediately visible to all the users (with the flag of "to be revised", of course).

Perhaps it could be added a parameter in LocalSettings.php in order to choose wether show the page as in current version of FlaggedRevs or to show instead a simple placeholder (something like "This is a new page and needs to be revised"). I'd not bother to change the colors of the links.

Tacsipacsi (talkcontribs)

Thank you for clearing your conception. (I don't know if anyone's going to implement it.)

Reply to "Creating new page"
Malarz pl (talkcontribs)

How can i check via API who reviewed specific revision? I'd like to have revision history with information which revision was flagged and who did it.

Tacsipacsi (talkcontribs)

It can be queried with the page history (example query). It seems to be available only with prop=revisions (not with list=allrevisions).

Malarz pl (talkcontribs)

Thanks for help. I added rvprop-flagged to API:Revisions.

Reply to "API"
Bennkenn (talkcontribs)

I installed the latest version of FlaggedRevs on my wiki which is 1.25.1. When I go and accept a revision on an editable page it says No Such Special Page. I'm not sure what I did wrong or what I need to change.

Nemo bis (talkcontribs)

Do you see the special page in "Special:SpecialPages" on your wiki?

Пика Пика (talkcontribs)

Have the same problem with MediaWiki 1.25.3 and FlaggedRevs REL1_25 2015-06-16T21:07:19. I can't see anything suspicious in the logs, and reviewing works, but the special pages related to FlaggedRevs have disappeared.

Ibutakov.smartec (talkcontribs)

I have found the cause of that problem: some extensions cannot create special pages if inside LocalSettings.php $wgGroupPermissions['*']['read'] = false; is set. so not working on private wiki.

btw i have same problem on 1.26.2 (latest stable)

Reply to "No Such Special Page"
Ата (talkcontribs)

User rights are extremely confusing.

  • autoreview receives autoreview right,
  • editor receives review as his main right (why is he not reviewer then?),
  • reviewer receives validate as his main right (why is he not validator then?).

Years extension enabled in uk.wiki I am still confused.

Reply to "User rights"
ParaSigma (talkcontribs)

What's this table role and how to prevent it's overgrowing?

Reply to "Size of 'flaggedrevs_statistics'"

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

4
198.214.211.107 (talkcontribs)

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.106 (talkcontribs)

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.

Aaron Schulz (talkcontribs)

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

Bruno Spy (talkcontribs)

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)

Reply to "Show non-checked page version until review = quality or higher"
Bob.spencer (talkcontribs)

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?

This post was posted by Bob.spencer, but signed as Sdsolutions.

Reply to "FlaggedRevs with AutoWikiBrowser"

Everyone sees Edit Review widget after installation

2
Edga~mediawikiwiki (talkcontribs)

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?

This post was posted by Edga~mediawikiwiki, but signed as Edga.

Jackmcbarn (talkcontribs)

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.

Reply to "Everyone sees Edit Review widget after installation"

How to organize chain of several approvals for one page

1
195.205.47.232 (talkcontribs)

Hi,

I need to organize in private wiki following workflow for page acceptance or return to lower level: user A can accept and send page to user B user B can accept and send page to user C or can return page to user A user C can accept and send page to user D or can return page to user B user D can accept and send page to user E or can return page to user C user E can accept and send page to user F or can return page to user D user F can accept and send page to see by anonymous readers (without login) or can return page to user E Thanks for reply in advance Peter

This post was posted by 195.205.47.232, but signed as Peter195.

Reply to "How to organize chain of several approvals for one page"

After uninstall users still show FlaggedRevs groups

2
Rob Kam (talkcontribs)

After uninstalling FlaggedRevs, Special:ListUsers still shows users are in groups autoreview, editor and reviewer - although in plain text and no longer as links. How to remove these from the User list?

This post was posted by Rob Kam, but signed as Robkam.

Aaron Schulz (talkcontribs)

I don't know of any script to remove user groups. If you don't care about adding user rights log entries, then you can start maintenance/sql.php and issue a SQL statement like "DELETE FROM user_groups WHERE ug_group IN ('editor','reviewer','autoreview')". If there are many users you may want to add "LIMIT 100" to the end and keep running it until there are 0 affected rows.

Reply to "After uninstall users still show FlaggedRevs groups"