Last modified: 2013-12-06 06:53:43 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T52736, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 50736 - Provide a way to remove autoconfirmed status without caching enabled.
Provide a way to remove autoconfirmed status without caching enabled.
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
AbuseFilter (Other open bugs)
unspecified
All All
: Low enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
: easy
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-07-04 11:24 UTC by Riccardo Bello
Modified: 2013-12-06 06:53 UTC (History)
4 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Riccardo Bello 2013-07-04 11:24:02 UTC
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.
Comment 1 Bawolff (Brian Wolff) 2013-07-09 14:59:50 UTC
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 )

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links