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?
Give a user Editor but not autopatrol their edits
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.)
Missing Special Pages?
I noticed that some special pages are references by Flagged Revs but they are missing. How can I install those pages? THanks.
I had similar issues, I pulled the git version and not the distribution version.
Which pages are missing and where (on which wiki)? Special pages usually can't be "installed" but are automatically enabled while installing the extension.
Special:UnreviewedPages and Special:PendingChanges
They are referenced by the FR but I don't have those special pages and I get an error.
On which wiki don’t have you them? Here, of course, they don’t exist as FR is not installed on MediaWiki.org; it’s in use on just a few Wikimedia wikis, most notably the German Wikipedia.
I can confirm that none of the special pages mentioned here:
show up. I downloaded for MW version 1.29 from both the MW extension distributor as well as from git. There is no error, just a page stating that the special page does not exist.
This is a private wiki we are developing for a client. It's an internal info wiki not available to the public.
Then it’s more difficult to debug. What error do you get? What is in LocalSettings.php (if FR variables can be published)?
I get the default special page not found error
Custom Namespaces not recognised
I use a adapted Version of ExtraNamespaces but only the usual 3 Namespaces are recognized (Main, Files, Templates).
In the LocalSettings.php i have only configured Main and then the numbers from the custom namespaces (100, 102 ...). The custom namespaces are properly listed in the special page "Links to this site" for example.
I runned the updateStats.php script manually but with no effect. Any suggestions what might be the problem?
It appears that the config from FlaggedRevs.config.php is loaded and not the configuration set in LocalSettings.php. Any suggestions why?
Did you define
$wgFlaggedRevsNamespaces before including FlaggedRevs? Like this:
$wgFlaggedRevsNamespaces = [ NS_MAIN, 100, 102 ]; require_once "$IP/FlaggedRevs/FlaggedRevs.php";
Then by including FlaggedRevs, you overwrite the custom configuration, so simply move the namespace config below the inclusion.
No, the require once is decalred befor any configuration.
This is my configuration in LocalSettings.php
$wgFlaggedRefsNamespaces = array(NS_MAIN, 100, 102, 104, 106, 108, 110, 112, 114, 116, 118, 220, 222, 224, 226, 228);
$wgFlaggedRevsHandleIncludes = FR_INCLUDES_FREEZE;
$wgFlaggedRevsOverride = true;
$wgFlaggedRevsAutoReview = FR_AUTOREVIEW_CHANGES;
$wgFlaggedRevsTags = array(
'accuracy' => array( 'levels' => 2, 'quality' => 2, 'pristine' => 3 ),
$wgFlaggedRevsWhitelist = array('Main_Page');
It’s misspelled: the variable is called
$wgFlaggedRevsNamespeces. (Also, the
 notation is preferred instead of
array() in MediaWiki code, see my code sample above. The latter causes no problems, but the former is shorter and is more similar to other languages’ array notation.)
I'm having the same problem, even though I've used the right code, and just like your example.
User groups resetting after relogin
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?
Advanced Review Log Customization
Hi all, I was wondering how we could customize the Special:AdvancedReviewLog to show only selected users (more than one, about 5), instead of all reviews.
If anyone knows, please let me know.
Bulk approve pages?
I imported all the pages from out old wiki via dump/import. I now have to go through and accept them all. There's the api, but I can't just list all pages from all namespaces and approve them. I'm still fiddling, but if anyone has an Idea let me know.
I see on the maintenance subdirectory of the extension there's a reviewAllPages.php
You may be able to mark all as reviewed executing this script from the console
tone, style, or Readability?
The article refers to "tone", but the current extension actually uses "style", not "tone". In the database, ft_tags has values like "accuracy:2\ndepth:2\nstyle:2\n". In the user interface, however, the "style" tag is displayed as "Readability". Maybe older versions of the extension had "tone" rather than "style" or "Readability", I don't know. Anyway, the documentation doesn't correctly describe the current extension. If I understand correctly, all references in the documentation to "tone" should be changed to "style", and there should be a note explaining that "Readability" in the user interface corresponds to "style" in the database.
Problem with installation MW1.27
Hello. I've some troubles installing FlaggedRevs extension. I've followed the process (except the cron part §6.2) and when returning on the wiki I've the following message :
"A database query error has occurred. This may indicate a bug in the software."
I've checked the data base : there is a table called "approved_revs" with 5 lines.
I'm on a shared hosting (PHP 5.6.24).
Does anybody knows what I may try to do ?
I've ran the
maintenance/populateImageSha1.php script using the Maintenance extension with a new line in the metadata.ini. The message told me it ran succesfully.
"I've checked the data base : there is a table called "approved_revs" with 5 lines." sorry this has no link with the subjet
Set Manual:$wgShowExceptionDetails to true to see details about the error. I don't know what's the relation about the error and having to run the populateImageSha1.php script
I've set $wgShowExceptionDetails to true, but unfortunately, I've then a blank page. Even the message "A database query error has occurred. This may indicate a bug in the software." disappear.
You must have been messed something up in LocalSettings.php when adding $wgShowExceptionDetails, like introducing a syntax error. Common causes are a missing semicolon, a typo or introduction of garbage characters.
OK, you were wright, thanks. Anyway, I don't have any new message in addition of "A database query error has occurred. This may indicate a bug in the software."
Is it possible the update.php didn't run well : are there some new tables that should have been add in the wiki database ?
Here is the log for the update :
"Turning off Content Handler DB fields for this part of upgrade.
...have ipb_id field in ipblocks table.
...have ipb_expiry field in ipblocks table.
...already have interwiki table
...indexes seem up to 20031107 standards.
...have rc_type field in recentchanges table.
...index new_name_timestamp already set on recentchanges table.
...have user_real_name field in user table.
...querycache table already exists.
...objectcache table already exists.
...categorylinks table already exists.
...have pagelinks; skipping old links table updates
...have rc_ip field in recentchanges table.
...index PRIMARY already set on image table.
...have rc_id field in recentchanges table.
...have rc_patrolled field in recentchanges table.
...logging table already exists.
...have user_token field in user table.
...have wl_notificationtimestamp field in watchlist table.
...watchlist talk page rows already present.
...user table does not contain user_emailauthenticationtimestamp field.
...page table already exists.
...have log_params field in logging table.
...logging table has correct log_title encoding.
...have ar_rev_id field in archive table.
...have page_len field in page table.
...revision table does not contain inverse_timestamp field.
...have rev_text_id field in revision table.
...have rev_deleted field in revision table.
...have img_width field in image table.
...have img_metadata field in image table.
...have user_email_token field in user table.
...have ar_text_id field in archive table.
...page_namespace is already a full int (int(11)).
...ar_namespace is already a full int (int(11)).
...rc_namespace is already a full int (int(11)).
...wl_namespace is already a full int (int(11)).
...qc_namespace is already a full int (int(11)).
...log_namespace is already a full int (int(11)).
...have img_media_type field in image table.
...already have pagelinks table.
...image table does not contain img_type field.
...already have unique user_name index.
...user_groups table exists and is in current format.
...have ss_total_pages field in site_stats table.
...user_newtalk table already exists.
...transcache table already exists.
...have iw_trans field in interwiki table.
...wl_notificationtimestamp is already nullable.
...index times already set on logging table.
...have ipb_range_start field in ipblocks table.
...no page_random rows needed to be set
...have user_registration field in user table.
...templatelinks table already exists
...externallinks table already exists.
...job table already exists.
...have ss_images field in site_stats table.
...langlinks table already exists.
...querycache_info table already exists.
...filearchive table already exists.
...have ipb_anon_only field in ipblocks table.
...index rc_ns_usertext already set on recentchanges table.
...index rc_user_text already set on recentchanges table.
...have user_newpass_time field in user table.
...redirect table already exists.
...querycachetwo table already exists.
...have ipb_enable_autoblock field in ipblocks table.
...index pl_namespace on table pagelinks includes field pl_from.
...index tl_namespace on table templatelinks includes field tl_from.
...index il_to on table imagelinks includes field il_from.
...have rc_old_len field in recentchanges table.
...have user_editcount field in user table.
...page_restrictions table already exists.
...have log_id field in logging table.
...have rev_parent_id field in revision table.
...have pr_id field in page_restrictions table.
...have rev_len field in revision table.
...have rc_deleted field in recentchanges table.
...have log_deleted field in logging table.
...have ar_deleted field in archive table.
...have ipb_deleted field in ipblocks table.
...have fa_deleted field in filearchive table.
...have ar_len field in archive table.
...have ipb_block_email field in ipblocks table.
...index cl_sortkey on table categorylinks includes field cl_from.
...have oi_metadata field in oldimage table.
...index usertext_timestamp already set on archive table.
...index img_usertext_timestamp already set on image table.
...index oi_usertext_timestamp already set on oldimage table.
...have ar_page_id field in archive table.
...have img_sha1 field in image table.
...protected_titles table already exists.
...have ipb_by_text field in ipblocks table.
...page_props table already exists.
...updatelog table already exists.
...category table already exists.
...category table already populated.
...have ar_parent_id field in archive table.
...have user_last_timestamp field in user_newtalk table.
...protected_titles table has correct pt_title encoding.
...have ss_active_users field in site_stats table.
...ss_active_users user count set...
...have ipb_allow_usertalk field in ipblocks table.
...pl_namespace, tl_namespace, il_to indices are already UNIQUE.
...change_tag table already exists.
...tag_summary table already exists.
...valid_tag table already exists.
...user_properties table already exists.
...log_search table already exists.
...have log_user_text field in logging table.
...l10n_cache table already exists.
...index ls_field_val already set on log_search table.
...index change_tag_rc_tag already set on change_tag table.
...have rd_interwiki field in redirect table.
...transcache tc_time already converted.
...*_mime_minor fields are already long enough.
...iwlinks table already exists.
...index iwl_prefix_title_from already set on iwlinks table.
...have ul_value field in updatelog table.
...have iw_api field in interwiki table.
...iwl_prefix key doesn't exist.
...have cl_collation field in categorylinks table.
...module_deps table already exists.
...ar_page_revid key doesn't exist.
...index ar_revid already set on archive table.
...ll_lang is up-to-date.
...user_last_timestamp is already nullable.
...index user_email already set on user table.
...up_property in table user_properties already modified by patch patch-up_property.sql.
...uploadstash table already exists.
...user_former_groups table already exists.
...index type_action already set on logging table.
...have rev_sha1 field in revision table.
...batch conversion of user_options: nothing to migrate. done.
...user table does not contain user_options field.
...have ar_sha1 field in archive table.
...index page_redirect_namespace_len already set on page table.
...have us_chunk_inx field in uploadstash table.
...have job_timestamp field in job table.
...index page_user_timestamp already set on revision table.
...have ipb_parent_block_id field in ipblocks table.
...index ipb_parent_block_id already set on ipblocks table.
...category table does not contain cat_hidden field.
...have rev_content_format field in revision table.
...have rev_content_model field in revision table.
...have ar_content_format field in archive table.
...have ar_content_model field in archive table.
...have page_content_model field in page table.
Content Handler DB fields should be usable now.
...site_stats table does not contain ss_admins field.
...recentchanges table does not contain rc_moved_to_title field.
...sites table already exists.
...have fa_sha1 field in filearchive table.
...have job_token field in job table.
...have job_attempts field in job table.
...have us_props field in uploadstash table.
...ug_group in table user_groups already modified by patch patch-ug_group-length-increase-255.sql.
...ufg_group in table user_former_groups already modified by patch patch-ufg_group-length-increase-255.sql.
...index pp_propname_page already set on page_props table.
...index img_media_mime already set on image table.
...iwl_prefix_title_from index is already non-UNIQUE.
...index iwl_prefix_from_title already set on iwlinks table.
...have ar_id field in archive table.
...have el_id field in externallinks table.
...have rc_source field in recentchanges table.
...index log_user_text_type_time already set on logging table.
...index log_user_text_time already set on logging table.
...have page_links_updated field in page table.
...have user_password_expires field in user table.
...have pp_sortkey field in page_props table.
...recentchanges table does not contain rc_cur_time field.
...index wl_user_notificationtimestamp already set on watchlist table.
...have page_lang field in page table.
...have pl_from_namespace field in pagelinks table.
...have tl_from_namespace field in templatelinks table.
...have il_from_namespace field in imagelinks table.
...img_major_mime in table image already modified by patch patch-img_major_mime-chemical.sql.
...oi_major_mime in table oldimage already modified by patch patch-oi_major_mime-chemical.sql.
...fa_major_mime in table filearchive already modified by patch patch-fa_major_mime-chemical.sql.
...user_id is already unsigned int.
...rc_comment in table recentchanges already modified by patch patch-editsummary-length.sql.
...hitcounter doesn't exist.
...site_stats table does not contain ss_total_views field.
...page table does not contain page_counter field.
...msg_resource_links doesn't exist.
...msg_resource doesn't exist.
...bot_passwords table already exists.
...have wl_id field in watchlist table.
...cl_collation key doesn't exist.
...index cl_collation_ext already set on categorylinks table.
...site_stats is populated...done.
Ok, maybe the right setting here is $wgShowSQLErrors = true;
OK it works. The error is :
- Query: SELECT page_id,page_namespace,page_title,page_restrictions,page_is_redirect,page_is_new,page_random,page_touched,page_links_updated,page_latest,page_len,page_content_model,fpc_override,fpc_level,fpc_expiry,fp_pending_since,fp_stable,fp_reviewed FROM `HELIOCENTRIXpage` LEFT JOIN `HELIOCENTRIXflaggedpages` ON ((fp_page_id = page_id)) LEFT JOIN `HELIOCENTRIXflaggedpage_config` ON ((fpc_page_id = page_id)) WHERE page_namespace = '0' AND page_title = 'Accueil' LIMIT 1
- Error: 1146 Table 'gditrisk_heliocentrix.HELIOCENTRIXflaggedpages' doesn't exist (localhost)
So the flaggedpages table doesn't exist. I don't understand why : I've followed all the steps of the installation. May the problem come from the fact that I'm on a shared host ?
From the output of the update.php process, apparently it hasn't populated any of the tables/fields of this extension. I'm not sure why.
FlaggedRevsUpdater.hooks.php contains the instructions to update the database, which in turn runs some of the scripts in the folders. You could run them manually but that's far from ideal, and you'll need to manually add the table prefix you're using.
Question to set Site to Sighted
It's working now.
I can´t set a page to "Sighted". I have not the box with buttons at the bottom of an article.
I want this box with the "Sighted"-Button. https://upload.wikimedia.org/wikipedia/commons/2/2e/Flaggedrevs_review_bar.png
But i have a box where is "Prose" (with Average, Good and Excellent) and not "Accuracy".
I hope you understand me.
It is a Mediawiki, Version 1.26.2. it is on a Server in my Office. We will try to run a wiki for our Company. I have on every site in my Wiki a Button in the right upper corner an Image ( not sighted).
In the LocalSettings.php i have added this Lines: $wgFlaggedRevsStatsAge = false;
$wgGroupPermissions['sysop']['review'] = true; //allow administrators to review revisions
Nope, its empty
Then I have no idea, hopefully a developer will figure it out.
It´s working now!
I used a backup and installed the extension again. Now it is working.
Creating new page
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?
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.)
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?
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?
Is there a way to hide the new pages until they aren't revised?
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?
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.
Thank you for clearing your conception. (I don't know if anyone's going to implement it.)