Extension talk:FlaggedRevs

Jump to: navigation, search

About this discussion

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

Reply to "No Such Special Page"

Main, File and Template ns + Category, Module, User, Project and Help added

2
İncelemeelemani (talkcontribs)

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.

Nemo bis (talkcontribs)

That file must not be edited directly. Place your configuration in LocalSettings.php, adding the line

$wgFlaggedRevsNamespaces = array( NS_MAIN, NS_USER, NS_PROJECT, NS_FILE, NS_MODULE, NS_TEMPLATE, NS_HELP, NS_CATEGORY );

after the line calling FlaggedRevs.

Reply to "Main, File and Template ns + Category, Module, User, Project and Help added"
Malarz pl (talkcontribs)

Ad API talk:Main page#API and FlaggedRevs.

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

Zache (talkcontribs)

You can check if the article is reviewed with this: - https://fi.wikipedia.org/w/api.php?action=query&prop=info|flagged&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.

Malarz pl (talkcontribs)

Thanks. When I check oldreviewed I got dates of last edit and last stable version. It's all I need now.

Reply to "API and FlaggedRevs"
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"

Can FlaggedRevs be used to tame $wgRawHtml ?

2
Adrelanos (talkcontribs)

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?

I am concerned, that evil javascript could be used to steal the login cookie of an admin.

If admins could review the just textual diff before that rendered page is shown to anyone, then admins could just decline the edit if someone added some javascript that they don't like without running it in their browser before. Otherwise it's hard to prevent execution of javascript by non-admin editors.

Nemo bis (talkcontribs)

$wgRawHtml must not be used in a wiki where untrusted users can edit, period.

Reply to "Can FlaggedRevs be used to tame $wgRawHtml ?"
Arent (talkcontribs)

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

Kghbln (talkcontribs)

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.

Arent (talkcontribs)

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.

Kghbln (talkcontribs)

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

Nemo bis (talkcontribs)

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

Reply to "MW version"

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

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

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

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

Nemo bis (talkcontribs)

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

Gborgonovo (talkcontribs)

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

Reply to "Set up different Revs for different NS"
Avshukan (talkcontribs)

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?

Reply to "Class 'FlaggedRevs' not found"

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"