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?
- I downloaded the extension from its page.
- I unzipped it and than uploaded to the appriopriate folder on my server
- 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
- 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:
0 /xxx/koleje/public_html/y/includes/GlobalFunctions.php(3847): Hooks::run('LoadExtensionSc...', Array)
1 /xxx/koleje/public_html/y/includes/installer/DatabaseUpdater.php(69): wfRunHooks('LoadExtensionSc...', Array)
2 /xxx/koleje/public_html/y/includes/installer/DatabaseUpdater.php(120): DatabaseUpdater->__construct(Object(DatabaseMysql), false, NULL)
3 /xxx/koleje/public_html/y/includes/installer/DatabaseInstaller.php(256): DatabaseUpdater::newForDB(Object(DatabaseMysql))
4 /xxx/koleje/public_html/y/includes/installer/WebInstallerPage.php(525): DatabaseInstaller->doUpgrade()
5 /xxx/koleje/public_html/y/includes/installer/WebInstaller.php(254): WebInstaller_Upgrade->execute()
6 /xxx/koleje/public_html/y/mw-config/index.php(50): WebInstaller->execute(Array)
7 /xxx/koleje/public_html/y/mw-config/index.php(18): wfInstallerMain()
The system configuration is as follows:
- Apache version: 2.2.21
- PHP version: 5.2.17
- MySQL version: 5.0.45
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...
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.
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!
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:
$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 ... ?
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.
'k, a bit more awkward then I'd hoped, but I can work around that ... not a showstopper. But just to clarify:
- 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
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.
'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 ...
This extension shows diff between rewieved and current version above edit window. How to disable this feature?
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.
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?
You can change the '$flags = FlaggedRevs::quickTags( FR_CHECKED ); // Assume basic level' line I suppose.
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?
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?
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?
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.
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!
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.
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?
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?
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~
Is there a specific method I can use to do this?
Is/are there a setting/s I can use instead of a hook?
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 .
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!
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.
I'm not sure what the question is. Are you talking about category pages or pages in categories?
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.
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.
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.
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.
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!
Are you talking about Extension:VisualEditor when you say "new editor"?
I've never had problems with that extensions, neither installing and configuring it nor working with it.
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?
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.
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?
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).