Extension talk:FlaggedRevs

From MediaWiki.org
Jump to: navigation, search
An archive box Archives 
 

Contents

Thread titleRepliesLast modified
Error caused by FlaggedRevs when upgrading Wiki to 1.19812:40, 29 May 2013
Enabled (I think) but not doing anything ...900:14, 31 March 2013
How to disable diff overview211:46, 23 March 2013
new page hide until reviewed112:58, 26 February 2013
Approve all pages?301:11, 7 February 2013
New pages don't need approval100:06, 10 January 2013
After uninstall users still show FlaggedRevs groups100:05, 10 January 2013
First review date118:58, 28 November 2012
Mark reviewed pages as UNREVIEWED with the API101:50, 27 November 2012
confirmation101:49, 27 November 2012
Undefined index: demoted101:47, 27 November 2012
edits stopped working after installing FlaggedRevs for wiki v 1.18122:22, 6 November 2012
API hook to action=parse to default to the latest stable version117:11, 26 September 2012
How to do this "Your changes will be displayed to readers once an authorized user accepts them" for media wiki user when users edit any page.?104:28, 7 September 2012
Error in contribs101:26, 4 September 2012
Exclude Categories complete with articles414:19, 17 August 2012
$wgFlaggedRevsAutoReviewNew209:40, 9 August 2012
Problem after installation! [HELP]416:29, 10 July 2012
How to use?1609:47, 25 June 2012
How to automatically approve all pages after importing from another wiki?403:11, 12 June 2012
First page
First page		 Previous page
Previous page		 Last page
Last page

Error caused by FlaggedRevs when upgrading Wiki to 1.19

Hi! I've just upgraded my Wiki to 1.19 and everything works fine till I try to start 'FlaggedRevs' extension.

What and how I do?

  1. I downloaded the extension from its page.
  2. I unzipped it and than uploaded to the appriopriate folder on my server
  3. As I don't have a root access (I'm using a shared hosting) I tried to launch the web update in the way described in Manual:update.php
  4. I received the following information:

Warning: call_user_func_array() [<a href='function.call-user-func-array'>function.call-user-func-array</a>]: First argument is expected to be a valid callback, 'FlaggedRevsUpdaterHooks::addSchemaUpdates' was given in /home/koleje/public_html/y/includes/Hooks.php on line 216

An error occured: Detected bug in an extension! Hook FlaggedRevsUpdaterHooks::addSchemaUpdates failed to return a value; should return true to continue hook processing or false to abort. Backtrace:

  1. 0 /xxx/koleje/public_html/y/includes/GlobalFunctions.php(3847): Hooks::run('LoadExtensionSc...', Array)
  2. 1 /xxx/koleje/public_html/y/includes/installer/DatabaseUpdater.php(69): wfRunHooks('LoadExtensionSc...', Array)
  3. 2 /xxx/koleje/public_html/y/includes/installer/DatabaseUpdater.php(120): DatabaseUpdater->__construct(Object(DatabaseMysql), false, NULL)
  4. 3 /xxx/koleje/public_html/y/includes/installer/DatabaseInstaller.php(256): DatabaseUpdater::newForDB(Object(DatabaseMysql))
  5. 4 /xxx/koleje/public_html/y/includes/installer/WebInstallerPage.php(525): DatabaseInstaller->doUpgrade()
  6. 5 /xxx/koleje/public_html/y/includes/installer/WebInstaller.php(254): WebInstaller_Upgrade->execute()
  7. 6 /xxx/koleje/public_html/y/mw-config/index.php(50): WebInstaller->execute(Array)
  8. 7 /xxx/koleje/public_html/y/mw-config/index.php(18): wfInstallerMain()
  9. 8 {main}


The system configuration is as follows:

Apache version: 2.2.21
PHP version: 5.2.17
MySQL version: 5.0.45

Thanx in advance for all help and advices. Pawel Niemczuk (talk) 21:16, 26 June 2012 (UTC)

Pawel Niemczuk (talk)‎21:16, 26 June 2012

What version of FlaggedRevs is it?

Aaron (talk)‎05:02, 28 June 2012

On the day when I reported the error I downloaded (as I suppose) the newest version of FlaggedRevs from ist page using Git Master (snapshot was temporarily not working). Today I downloaded again FlaggedRevs v. 1.19 but this time using a snapshot. And again an error appeares. This time when I try to launch a web updater (after uploading FlaggedRevs to an appriopriate directory and adding the demanded line to LocalSettings.php) I get the following error:

Fatal error: Class 'FlaggedRevsUISetup' not found in /home/koleje/public_html/z/extensions/FlaggedRevs/FlaggedRevs.php on line 48

I presume I'm doing something wrong but I don't have the vauguest idea what I'm doing wrong...

Pawel Niemczuk (talk)‎04:09, 30 June 2012

That doesn't make much sense. That code line is almost right after the line " require( dirname( __FILE__ ) . '/frontend/FlaggedRevsUI.setup.php' );". If that file wasn't found, you would have had a different fatal, so it must exist.

Aaron (talk)‎19:10, 5 July 2012

Dear Aaron, it seems that all my problems were caused by an inappriopriate hosting. I've just moved to a different one (with a root-access) and everything works fine! Once again thanks a lot for your patience and attention!

Pawel Niemczuk (talk)‎18:40, 9 July 2012

Same here... I think my hoster is fine, I uploaded the extension and tried to update via the webinstall, leading to "Detected bug in an extension! Hook FlaggedRevsUpdaterHooks::addSchemaUpdates failed" :/

Pattyland (talk)‎20:23, 27 May 2013
Show 3 replies
 
 
 
 
 

Enabled (I think) but not doing anything ...

I've gone through what I think are the appropriate threads in this forum, as well as used search, but have to be missing something, because its still not working .. at least, I don't think it is.

First, installed from git, onto a mediawiki 1.20.3 install ... modified my LocalSettings.php file, to include:

== require_once("$IP/extensions/FlaggedRevs/FlaggedRevs.php");

$wgFlaggedRevsStatsAge = false; $wgFlaggedRevsExceptions = array( ); $wgFlaggedRevsAutoReview = FR_AUTOREVIEW_NONE; ==

And left the default set for:

$wgFlaggedRevsOverride = true;

So, if I'm reading right, any edit / new page has to go through a reviewer before its visible to anyone, logged in or not.

I have non-logged in allowed to edit (internal wiki, we just don't want to have to create user accounts for everyone *just in case* someone decides to want to edit) ...

when I go to a page on the site that doesn't exist, and click 'edit', it allows me to edit and save, but its instantly visible, no review required.

I went to the database itself and looked in the various flagged* tables, and nothing seems to be being written there either ... so figured I have to had missed a step in this process *somewhere* ...

Now, I may be mis-understanding the intent of this extension, but I'm hoping its just some flag I'm not noticing that needs to be set ... from reading through the threads here, I had found '$wgFlaggedRevsAutoReview = FR_AUTOREVIEW_NONE;' ... so is there maybe another that I haven't stumbled across yet ... ?

Thanks ...

142.32.208.237‎22:25, 20 March 2013

New unreviewed pages are always fully visible. FlaggedRevs only applies to pending edits to reviewed pages. It might be interesting to add a feature to not let google et all index new unreviewed pages, but hiding brand new pages is tricky to implement and be usable.

Aaron (talk)‎07:29, 21 March 2013

'k, a bit more awkward then I'd hoped, but I can work around that ... not a showstopper. But just to clarify:

  1. FR_AUTOREVIEW_NONE
  2. Don't auto-review any edits or new pages

Doesn't actually apply to "new pages" then ... ? Or am I mis-understanding what is meant by disabling auto-review?

But, that said, I just went to a page that I created previously as Anon, clicked the Edit button, added text to it and Saved ...

Again, its totally visible to the next Anon person to come along, and checking the database, still nothing in the flaggedrevs table:

mediawiki=# select * from flaggedrevs;

fr_rev_id | fr_rev_timestamp | fr_page_id | fr_user | fr_timestamp | fr_quality | fr_tags | fr_flags | fr_img_name | fr_img_timestamp | fr_img_sha1

+------------------+------------+---------+--------------+------------+---------+----------+-------------+------------------+-------------

(0 rows)

142.32.208.237‎17:17, 21 March 2013

A new page that is not reviewed/auto-reviewed acts almost the same with FlaggedRevs enabled as it does without it enabled. Even if autoreview is totally disabled, new pages will still be visible just like without FlaggedRevs. The extension only changes the workflow once a page actually as at least one reviewed version.

Aaron (talk)‎23:07, 25 March 2013

'k, we can definitely live with that ... the problem that I'm currently having is that I never seem to get any pages *for* review ... all the FlaggedRev tables seem to be empty, even after I create a new page *and* subsequently edit it again ... I'v checked my PostgreSQL server log for any SQL errors (ie. a missed column, duplicate key, etc) and its all totally clean ... which leads me to believe I've missed a setting somewhere ...

thoughts? direction?

142.32.208.226‎16:11, 26 March 2013

Do you have the review form on any pages? Nothing will go in any tables until revisions start getting reviewed by admins.

Aaron (talk)‎20:39, 26 March 2013
Show 4 replies
 
 
 
 
 

How to disable diff overview

This extension shows diff between rewieved and current version above edit window. How to disable this feature?

AS (talk)‎10:53, 2 October 2012

It should start off collapsed, so why is this a problem?

Aaron (talk)‎01:51, 27 November 2012

It's showed full after saving

AS (talk)‎11:46, 23 March 2013
 
 

new page hide until reviewed

I want to hide a page which is created by a user until it is sighted/reviewed. How could I do this? I have the latest versions.

Shiro175 (talk)‎12:37, 26 February 2013

done, $egApprovedRevsBlankIfUnapproved = true;

Shiro175 (talk)‎12:58, 26 February 2013
 

Approve all pages?

Is it possible to approve all pages at once? I know there is a maintenance script called "reviewAllPages.php" but this will only mark my pages as sighted. I want them to be approved. Maybe I can modify the reviewAllPages.php script?

Thanks!

Stefan‎13:18, 1 February 2013

You can change the '$flags = FlaggedRevs::quickTags( FR_CHECKED ); // Assume basic level' line I suppose.

Aaron (talk)‎01:03, 4 February 2013

Ok I tried this and changed the line to '$flags = FlaggedRevs::quickTags( FR_QUALITY ); // Assume basic level' but nothing changed, then I tried with '$flags = FlaggedRevs::quickTags( FR_PRISTINE ); // Assume basic level' and again nothing changed. I'm not really much of a coder :/
Do you have another suggestion what I could try to get all pages approved? Maybe an SQL Statement?

Thanks

Stefan‎07:55, 4 February 2013

What does var_dump( FlaggedRevs::quickTags( FR_QUALITY ) ); give in eval.php?

Aaron (talk)‎01:11, 7 February 2013
 
 
 

New pages don't need approval

When I create a new page, it seems to not be under rev. control. Only when the page is accepted for the first time, future changes are handled correctly. Is there any way to disable this behaviour?

213.235.220.170‎08:45, 27 December 2012

Set $wgFlaggedRevsAutoReview accordingly and make sure you have 'autoreview' rights.

Aaron (talk)‎00:06, 10 January 2013
 

After uninstall users still show FlaggedRevs groups

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?

Robkam (talk)‎19:12, 9 January 2013

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.

Aaron (talk)‎00:04, 10 January 2013
 

First review date

Is there ability to know the date of first page review? I want to use it with Semantic MediaWiki extension to show only reviewed pages on StartPage. Maybe some magic word (__FIRSTREVDATE__) or parser function? How can I use FlaggedRevs PHP classes to make magic word myself? Thanks alot!

91.225.116.75‎07:00, 31 October 2012

I'm not familiar enough with SMW I'm afraid.

Aaron (talk)‎18:58, 28 November 2012
 

Mark reviewed pages as UNREVIEWED with the API

Because of the workflow in our office....we have a need to mark reviewed pages as unreviewed. Not sure how to do that with the API. Any help is appreciated.

64.124.79.214‎18:19, 2 October 2012

See api.php (there is an 'unapprove' parameter for apireview). You cannot mark entire pages as unreviewed however.

Aaron (talk)‎01:50, 27 November 2012
 

confirmation

I want that: Our viki visitors can edit and create pages. But changes confirm by administrators and after content will be publish. if administrators is not confirm, changes will not show other visitors. How i make that?

Bekircem (talk)‎14:29, 4 October 2012

No you mean not show at all? That's harder to do. But if you want the last stable version of pages to show (unless the user clicks on a link to see the draft), than can be done via $wgFlaggedRevsOverride and $wgFlaggedRevsExceptions (see FlaggedRevs.config.php).

Aaron (talk)‎01:49, 27 November 2012
 

Undefined index: demoted

I got error message:

<b>Notice</b>:  Undefined index: demoted in <b>/home/receptdo/public_html/test/extensions/FlaggedRevs/backend/FlaggedRevs.hooks.php</b> on line <b>913</b><br />

What is the problem?

Luft-on (talk)‎17:18, 20 November 2012

What version of the code is used? It looks like the latest uses the "empty" function to avoid warnings.

Aaron (talk)‎01:47, 27 November 2012
 

edits stopped working after installing FlaggedRevs for wiki v 1.18

I installed FlaggedRevs usings "FlaggedRevs-5e5dc25.tar.gz" and it seemed to be going well until I tried to edit an article. It gave me the internal server error once I saved my changes. It happens for all users.

Any ideas? Stumped....

Thank you~ Michelle~

108.178.189.46‎22:09, 6 November 2012

Also, when I accept revisions, it doesn't stick. Meaning it still stays in "unaccepted" status.

Maybe I have a buggy version.

Can someone tell me where to go to download the stable version for wiki v 1.18?

108.178.189.46‎22:22, 6 November 2012
 

API hook to action=parse to default to the latest stable version

Is there a specific method I can use to do this?

Is/are there a setting/s I can use instead of a hook?

GHenle (talk)‎17:13, 6 September 2012

Not aware of one.

Aaron (talk)‎17:11, 26 September 2012
 

How to do this "Your changes will be displayed to readers once an authorized user accepts them" for media wiki user when users edit any page.?

I want that when any registered user want to contribute by editing my existing page the content edited by user should not directly display on the edited page or page created by any user should not be displayed directly first the user edited content should displayed after authorized user accepts them .

Nawalsaini (talk)‎11:25, 24 August 2012

You need to set $wgFlaggedRevsNamespaces to all the namespaces you want (see includes/defines.php).

Aaron (talk)‎04:28, 7 September 2012
 

Error in contribs

Hi, after I installed the FlaggedRevs extension, the following PHP warning turned up in the contribs page.

Warning: Missing argument 4 for FlaggedRevsUIHooks::addToContribsLine() in path/to/wiki/extensions/FlaggedRevs/frontend/FlaggedRevsUI.hooks.php on line 495 
Warning: Cannot modify header information - headers already sent by (output started at path/to/wiki/extensions/FlaggedRevs/frontend/FlaggedRevsUI.hooks.php:495) in path/to/wiki/includes/WebResponse.php on line 38

The first line repeats for every edit shown in the contribs page. Could anybody help me with this? Thanks!

Cloud668 (talk)‎07:18, 28 August 2012

Maybe the extension and core mediawiki version don't match?

Aaron (talk)‎01:26, 4 September 2012
 

Exclude Categories complete with articles

Hey,

is it possible to exclude Categories complete with articles from reviewing? I would like to exempt categories including subcategories and pages from reviewing. Or am i allowed to define special categories for reviewing?

I only find the config: $wgFlaggedRevsWhitelist = array( 'Main_Page' );

Thanks a lot.

85.232.7.145‎12:12, 14 August 2012

I'm not sure what the question is. Are you talking about category pages or pages in categories?

Aaron (talk)‎19:46, 14 August 2012

Hey Aaron,

I mean both, category pages and normal pages in categories. F. e. we have a "category:cookbook" with more than 100 pages (recipes). This category including all subcategories and pages should not be reviewed.

Do I have to write every pagename in the function

$wgFlaggedRevsWhitelist = array( 'recipe1', 'recipe2' ... 'recipe100' );

or is there a smarter way?

Thanks a lot.

85.232.7.145‎09:31, 15 August 2012

There is no feature to whitelist all pages in a category. The way category membership is tied to parsing would make this trickly/slow to implement.

Aaron (talk)‎21:07, 15 August 2012

Hey Aaron,

thanks for your help. Have a nice weekend.

85.232.7.145‎14:19, 17 August 2012
 
 
 
 

$wgFlaggedRevsAutoReviewNew

Hi. Checking the NOC file (section 'fiwiki') I've found the variable $wgFlaggedRevsAutoReviewNew = true; but I couldn't find here the meaning of that variable. What it does? Is the same as $wgFlaggedRevsAutoReview = FR_AUTOREVIEW_CREATION_AND_CHANGES; ? Thanks.

--Marco Aurelio (talk • meta)‎16:11, 8 August 2012

Setting that var sets FR_AUTOREVIEW_CREATION. If $wgFlaggedRevsAutoReview === true as well, then it's like FR_AUTOREVIEW_CREATION_AND_CHANGES. $wgFlaggedRevsAutoReview is best configured as a bitfield but the old ways still work.

Aaron (talk)‎19:19, 8 August 2012

Thanks - I planned to set in the config

$wgFlaggedRevsAutoReview = FR_AUTOREVIEW_CREATION_AND_CHANGES;

So that just folks with the autoreview permission (plus editors, reviewers, admins, etc...) could have their edits and page creations automatically marked as sighted.

--Marco Aurelio (talk • meta)‎09:40, 9 August 2012
 
 

Problem after installation! [HELP]

Hello!
MediaWiki Version: 1.19.1

Well, after installing this extension I found two problems on my wiki:
1 - The sortable option on DPL lists don't work anymore.
2 - The new editor don't work 100% (see)

Someone can help me to solve this problems?
Thanks in advance!

177.64.76.59‎22:53, 7 July 2012

Are you talking about Extension:VisualEditor when you say "new editor"?

Jasper Deng (talk)‎00:27, 8 July 2012
 

...or maybe about the Extension:WikiEditor?

Helder‎14:43, 8 July 2012

Sorry, I forgot it. Is Extension:WikiEditor.

177.64.76.59‎17:22, 8 July 2012
 

Hello, I found the bug and fixed, thanks for the attention.

177.64.76.59‎16:29, 10 July 2012
 

How to use?

I can find no way to use this extension. Help me here?

HTFFanBrandon04 (talk)‎04:57, 26 March 2012

It's complicated. So, what exactly is your problem here?

Jasper Deng (talk)‎05:01, 26 March 2012

I don't know how to use this extension. It's complicated!

HappyTreeFriends (my home page or talk 2 me)‎10:12, 9 April 2012
 

I've never had problems with that extensions, neither installing and configuring it nor working with it.

Tim (SVG)‎11:15, 9 April 2012

Oh, you probably know I was using a different signature. That's HTFFanBrandon04's new signature. And how do I use the extension? Did I miss a requirement? What do I have to do?

HappyTreeFriends (my home page or talk 2 me)‎12:08, 9 April 2012

The only thing you can miss is adding the SQL tables.

Tim (SVG)‎12:14, 9 April 2012

What is an "SQL table", and what does "SQL" stand for? I use SQLite, a very lightweight database system as an alternative to MySQL. So a database is needed to store revision flagging statistics? I already have an SQLite database file! Give me all the information about the SQL tables, maintenance scripts, etcetera. All for this extension, FlaggedRevs, allowing you to vote revisions of a page.

HappyTreeFriends (my home page or talk 2 me)‎14:24, 9 April 2012

You just need to import /extensions/FlaggedRevs/schema/mysql/FlaggedRevs.sql (path for MW 1.18, trunk's path is /extensions/FlaggedRevs/backend/schema/mysql/FlaggedRevs.sql) or you run update.php.

Tim (SVG)‎14:47, 9 April 2012
Show 9 replies
 
 
 
 
 

How to automatically approve all pages after importing from another wiki?

subj.

Serdtsev (talk)‎13:57, 8 June 2012

You could try to adapt a JavaScript such as wikibooks:pt:MediaWiki:Gadget-MassReview.js for your specific needs.

Helder‎15:34, 8 June 2012

Hi Helder, Thanks for fast answered.

What is the language of the text in this script? Portuguese? How to use this script after adding in the gadgets?

Serdtsev (talk)‎07:13, 9 June 2012

Yes, it is Portuguese.

The script will add a link in the top right of the pages (in the same portlet menu where the "move" link is). If you click the link it will ask for a number of pages to review. Then it will get a list of unreviewed pages from MediaWiki API and check each of them to see if the last edit was made by a user listed in the variable "admins" (mostly sysops in the case of Portuguese Wikibooks, but in essence the list should consist of trusted users from your wiki).

Helder‎11:46, 9 June 2012
 
 

The is a script to review all pages in FlaggedRevs/maintenance.

Aaron (talk)‎03:11, 12 June 2012
 
First page
First page		 Previous page
Previous page		 Last page
Last page
Retrieved from "http://www.mediawiki.org/w/index.php?title=Extension_talk:FlaggedRevs&oldid=622659#How_to_automatically_approve_all_pages_after_importing_from_another_wiki.3F_16258"