Last modified: 2013-07-04 11:02:42 UTC
Steps to reproduce: 1) Create an easy filter like action == 'edit' & ("username" in user_name) typing your username in "username" 2) Select "Revoke the user's autoconfirmed status" 3) Save 4) Edit or create a page. Expected result: The user is no longer autoconfirmed. Result: The user is still autoconfirmed.
The website on which I'm encountering this bug is the one indicated in the URL. You need to create an account.
Note that, with the recent default config, (2) requires abusefilter-modify-restricted permission In the abuse log I see that the extension claims to execute the action on the target; it is to be seen whether it actually works.
On my wiki it doesn't work. I tried with testwiki - filter #1 typing "the abuse filter will block this" - and it did block me. All the sysops on my wiki have abusefilter-modify-restricted, this function is not available for any group on testwiki.
The reason for this bug was that cache was not enabled on that wiki. It works setting CACHE_DB. Closing this bug as RESOLVED INVALID, but opening another bug to request the feature to remove autoconfirmed status without cache enabled.
