Provide a way to remove autoconfirmed status without caching enabled.
Open, LowPublicFeature
Actions

Assigned To

None

Authored By

	• bzimport
	Jul 4 2013, 11:24 AM

Description

Author: bello.a

Description:
AbuseFilter's feature "Revoke autoconfirmed status" only works if caching is enabled. Is it possible to add a feature to revoke autoconfirmed status without caching enabled? The only way I found to do this was to create a group with only $wgRevokePermissions['deautoconfirmed']['action'] = true; for all the actions allowed in autoconfirmed. Then I created a new action in AbuseFilter, and it worked. That's not the best solution, but.

Version: unspecified
Severity: enhancement

Details

Reference: bz50736

Event Timeline

• bzimport raised the priority of this task from to Low.Nov 22 2014, 1:43 AM

• bzimport added projects: AbuseFilter, good first task.

• bzimport set Reference to bz50736.

• bzimport added a subscriber: Unknown Object (MLST).

• bzimport created this task.Jul 4 2013, 11:24 AM

Technical summary:
*Abusefilter revokes autoconfirm status by saving stuff in $wgMemc
*By default (depending on your $wgMainCacheType) that's a no-op
*It should (probably) be using instead wfGetCache( CACHE_ANYTHING )

• werdna unsubscribed.Dec 10 2014, 6:16 PM

I wouldn't say this is a good first bug. Something has changed in the meanwhile, and I don't know if it's worth it to change this behaviour. Also, it should be noted that we don't explicitly require caching for blockautopromote (like we do for throttle).

Aklapper changed the subtype of this task from "Task" to "Feature Request".Feb 4 2022, 11:13 AM

Aklapper removed a subscriber: • wikibugs-l-list.

Provide a way to remove autoconfirmed status without caching enabled.Open, LowPublicFeatureActions

Description

Details

Event Timeline

Provide a way to remove autoconfirmed status without caching enabled.
Open, LowPublicFeature
Actions