Page MenuHomePhabricator

Allow configuration variable setting for "Special:ActiveUsers" (active user)
Open, Needs TriagePublicFeature

Description

So, currently to be an "active user" and be listed on Special:ActiveUsers, you need to have 1 action in 30 days.

I personally think that this would not fit the definition of "active", but that is up to each wiki administrator. Therefore, I think that a configuration variable should be (re)added, for example $wgActiveUserEditCount (which existed previously) to be able to allow each wiki to set their own threshold for an active user instead of being forced to stick to this default value.

I also propose we set the default value to something more decent, such as 10 actions (proposed by @Skizzerz in MediaWiki-General)

Related Objects

Event Timeline

DannyS712 changed the subtype of this task from "Task" to "Feature Request".Dec 11 2019, 3:47 AM
DannyS712 added subscribers: demon, DannyS712.

The duration is already configurable: $wgActiveUserDays (default is 30, but can be adjusted)
As for a minimum number of edits / actions, adding 'HAVING COUNT(rc_id) > ' . $dbr->addQuotes( $this->getConfig()->get( 'ActiveUserEdits' ) ) or something similar to the query may be enough

I'll note that, historically, $wgActiveUserEditCount wasn't a part of the query:

@demon care to chime in (you added and removed)?

The duration is already configurable: $wgActiveUserDays (default is 30, but can be adjusted)
As for a minimum number of edits / actions, adding 'HAVING COUNT(rc_id) > ' . $dbr->addQuotes( $this->getConfig()->get( 'ActiveUserEdits' ) ) or something similar to the query may be enough

I'll note that, historically, $wgActiveUserEditCount wasn't a part of the query:

@demon care to chime in (you added and removed)?

Sorry for the very late response, but what exactly do you mean by adding it to the query? What I meant was to be able to configure it as a setting in LocalSettings.php

It's probably both. There would have to be new configuration settings read in LocalSettings and then code that change the actual database query that happens in the background, based on those new config options.