Extension talk:FlaggedRevs

Archives

Archive 1 Archive 2 Archive 3

Previous page history was archived for backup purposes at Extension talk:FlaggedRevs/LQT Archive 1 on 2015-07-10.

I am on MW version 1.34 and a, trying to use the 1.31 version of FlaggedRevs. When trying to run the update.php maintenance script I am getting the following error:

PHP Fatal error:  Uncaught Exception: Unable to open file /opt/bitnami/apps/mediawiki/htdocs/extensions/FlaggedRevs/extension.json: filemtime(): stat failed for /opt/bitnami/apps/mediawiki/htdocs/extensions/FlaggedRevs/extension.json in /opt/bitnami/apps/mediawiki/htdocs/includes/registration/ExtensionRegistry.php:136

Stack trace:

#0 /opt/bitnami/apps/mediawiki/htdocs/includes/GlobalFunctions.php(52): ExtensionRegistry->queue('/opt/bitnami/ap...')

#1 /opt/bitnami/apps/mediawiki/htdocs/LocalSettings.php(440): wfLoadExtension('FlaggedRevs')

#2 /opt/bitnami/apps/mediawiki/htdocs/includes/Setup.php(124): require_once('/opt/bitnami/ap...')

#3 /opt/bitnami/apps/mediawiki/htdocs/maintenance/doMaintenance.php(83): require_once('/opt/bitnami/ap...')

#4 /opt/bitnami/apps/mediawiki/htdocs/maintenance/update.php(277): require_once('/opt/bitnami/ap...')

#5 {main}

  thrown in /opt/bitnami/apps/mediawiki/htdocs/includes/registration/ExtensionRegistry.php on line 136

Does anyone know why I am getting this error?

Thank you

Perhaps the file /opt/bitnami/apps/mediawiki/htdocs/extensions/FlaggedRevs/extension.json does not exist, or the server doesn't have read permissions to open that file

You should use

require_once "$IP/extensions/FlaggedRevs/FlaggedRevs.php";

and not

wfLoadExtension('FlaggedRevs')

as the extension documentation instructs you to do.

That worked, thank you!

Okay one more question, I am getting the following error:

[dd7f92a2ded44d8eb30257a8] /Main_Page Error from line 58 of /opt/bitnami/apps/mediawiki/htdocs/extensions/FlaggedRevs/backend/FRUserActivity.php: Call to undefined method ObjectCache::getMainStashInstance()

From what I can find this may be due to mismatched versions, but I am using the most recent version that I am able from the extension page's download options. Any suggestions on this?

Indeed, this method was removed in MediaWiki 1.34, so the FlaggedRevs version for MediaWiki 1.31 could use it with no problem, but it fails on your MW 1.34. You can download FlaggedRevs version for MW 1.34 from GitHub, but I strongly suggest that you update to MediaWiki 1.35 LTS (and FlaggedRevs for MW 1.35), since MediaWiki 1.34 isn’t supported since November 2020. (By the way, this may be the reason why FlaggedRevs for MW 1.34 cannot be downloaded with ExtensionDistributor, while FlaggedRevs for MW 1.35 is available there.)

Unfortunately the 1.34 branch is not compatible with Mediawiki 1.34 (not sure why) so it looks like my only option is upgrade MW or not use it.

Hi, is there any variables for FlaggedRevs ext. that could be retrieved by mw.config object?

If you're on a page with FlaggedRevs active, there's wgStableRevisionId and, if it's not empty, wgFlaggedRevsParams. These were always present before https://gerrit.wikimedia.org/r/c/mediawiki/extensions/FlaggedRevs/+/508427. I think that's it; I previously put in a task for wgFlaggedRevsNamespaces.

thx @Amorymeltzer

Is it possible to optionally add an expiry time for PendingChanges tags. The purpose is to add a time delay before newbie edits go live and a vandalism patroller can immediately approve or reject that edit.

This time delay will help Vandalism patrollers and watchlisters to accept or revert newbie edits before they become live. It is intended for all edits in a wiki. Unreviewed edits can go live after the delay time (eg 2 hours), so that there will not be any backlog or a conflict with "editable by anyone" policy. It will facilitate a better alternative to en:WP:Delayed revisions

I guess the reviewAllPages.php maintenance script could be modified to add an option to only review changes older than X time. Then you can add this script as a cron job every day.

I am actually asking for a time based autoacceptance

I have added a feature request at Phabricator: https://phabricator.wikimedia.org/T267642

Ciencias proposal would be time based autoacceptence. An implementation via bot would be an easy alternative.

Does FlaggedRevs works with Wikibase and its Items and Properties?

We have "Flagged Reviews" (Pending Changes) installed at Hebrew Wikisource.

One difficulty with the current installation is this: When a change is made within a template (or in a page that is used within other pages), all of the pages that use it (sometimes hundreds or thousands of them) show a notice at the top about changes in the template that need to be approved in order to rate the current version of the page. This happens even if the page itself has not been changed and the newer version of the template was already approved!

Is there currently a way to configure the extension so that if changes are made to a template/page that appears within other pages are approved, then the pages that use it will simply remain at their current level of approval?

MediaWiki1.34.0 (ae6e0c0)

Flagged Revision – (784dad

---

Hi,

can someone explain to me what does this mean?

Undefined index: excludeLastDays in /var/www/w/extensions/FlaggedRevs/FlaggedRevsSetup.php on line 78

It appears every time I run the update maintenance script (and other related stuff).

Thanks.

Looks like $wgFlaggedRevsAutopromote doesn't contain the 'excludeLastDays' key.

If you've defined $wgFlaggedRevsAutopromote in LocalSettings.php be sure you define it correctly and without clearing the entire array

Hi,

for the benefit of complete and detailed information, the warnings were all these:

PHP Notice:  Undefined index: excludeLastDays in /var/www/w/extensions/FlaggedRevs/FlaggedRevsSetup.php on line 78

PHP Notice:  Undefined index: excludeLastDays in /var/www/w/extensions/FlaggedRevs/FlaggedRevsSetup.php on line 93

PHP Notice:  Undefined index: totalCheckedEdits in /var/www/w/extensions/FlaggedRevs/FlaggedRevsSetup.php on line 97

PHP Notice:  Undefined index: excludeLastDays in /var/www/w/extensions/FlaggedRevs/FlaggedRevsSetup.php on line 98

PHP Notice:  Undefined index: maxRevertedEditRatio in /var/www/w/extensions/FlaggedRevs/FlaggedRevsSetup.php on line 101

PHP Notice:  Undefined index: neverBlocked in /var/www/w/extensions/FlaggedRevs/FlaggedRevsSetup.php on line 104

but thanks to your clue, I found out that in /var/www/w/extensions/FlaggedRevs/ there is beautiful README file that reads like this:

In 1.34 the autopromote config was removed from the default. If you want to keep the same config

add the following to your LocalSettings.php

<source lang="php">

$wgFlaggedRevsAutopromote = [

        'days'                  => 60, # days since registration

        'edits'                 => 250, # total edit count

        'excludeLastDays'       => 1, # exclude the last X days of edits from below edit counts

        'benchmarks'            => 15, # number of "spread out" edits

        'spacing'               => 3, # number of days between these edits (the "spread")

        'totalContentEdits'     => 300, # edits to pages in $wgContentNamespaces

        'totalCheckedEdits'     => 200, # edits before the stable version of pages

        'uniqueContentPages'    => 14, # unique pages in $wgContentNamespaces edited

        'editComments'          => 50, # number of manual edit summaries used

        'userpageBytes'         => 0, # size of userpage (use 0 to not require a userpage)

        'neverBlocked'          => true, # username was never blocked before?

        'maxRevertedEditRatio'  => 0.03, # max fraction of edits reverted via "rollback"/"undo"

];

</source>

I did changed my LocalSettings.php and now everything is fine with FR.

Perhaps the installation/configuration instructions deserve some attention and some updates.

Thank you so much @Ciencia Al Poder

I find funny to see a README file with wiki syntax (that can't be rendered nicely in any text editor btw) but then devs fail to update that documentation on the wiki page... Maybe @Reedy can check if the instructions are correct, since it seems he was the author of those changes in the README

Hi,

it used to be possible to set $wgFlaggedRevsTags to some value and that would be used for the tags. Since some release arrays defined in LocalSettings are merged with the array defined in extension.json and there seems to be no way to remove a value anymore.

FlaggedRevs itself does even support an empty $wgFlaggedRevsTags, but there seems no way to set this anymore.

Any hints?

I tried to dump my wiki into an XML and import it into a fresh installation. But FlaggedRevs weren moved too.

I used mediawiki's onboard maintenance scripts.

How would I fix that...?

Unfortunately the out-of-the-box tools of MediaWiki allow only to export "the lastest stable version", but not "all revisions with their flags". Additionally, the import does not know anything about flags.

I want to protect some pages using `action = stabilize`, but I need to check for their current status (expiray, reason, level, etc.). Is there any way to get these info using API?

Found it: https://www.mediawiki.org/w/index.php?title=Extension:FlaggedRevs&diff=3274706&oldid=3214539

I've set $wgFlaggedRevsExceptions = [ '*' ]; for everyone see the latest edit. But this doesn't work.

I've resolved this. I used $wgFlaggedRevsOverride and I set this to false.

$wgFlaggedRevsOverride = false;