That's it. In those wikis, no one can effectively enable block for any abusefilter. I'm filing this task as a reminder, since I still have to determine which exact wikis are affected and probably ask on their AF requests page who should have this right.
Description
Description
Details
Details
Related Objects
Related Objects
- Mentioned In
- T226987: Missing abusefilter-log-private right in $wgGrantPermissions
T191740: Bundle AbuseFilter extension with MediaWiki - Mentioned Here
- rEABFe9422c5c92cb: Rearrange config to provide better experience
T191740: Bundle AbuseFilter extension with MediaWiki
T226987: Missing abusefilter-log-private right in $wgGrantPermissions
rOMWC7e95f6d84299: Update AbuseFilter config to keep the status quo
T178284: Make $wgGroupPermissions['sysop']['abusefilter-modify-restricted'] = true; default in WMF wikis
Event Timeline
Comment Actions
Affected:
- enwikinews
- itwikinews
I also see that when wmfRealm is 'labs', the action 'block' is enabled but the right is not assigned. However, I actually don't know which sites are affected by this. I'll ask in the appropriate pages of the 2 wikinews above, while waiting for someone who knows what to do with labs.
Comment Actions
I think I had a task filed somewhere for this very issue (cannot find it right now; will keep searching).
Comment Actions
Found it finally: T178284: Make $wgGroupPermissions['sysop']['abusefilter-modify-restricted'] = true; default in WMF wikis. Self-declined.
Comment Actions
@MarcoAurelio Thanks for pointing it out. Your comment reminded me that I actually submitted a patch with such change, plus some other config rearrangements (https://gerrit.wikimedia.org/r/#/c/mediawiki/extensions/AbuseFilter/+/468696/) with the goal of making sysadmins' life easier. As for the state of this task: my message on enwikinews got no answer. The one on itwikinews got one saying 'sysop' is fine, but nothing else. Probably, we should just wait for the other patch to be merged, so that this problem won't be a thing anymore, in any existing wiki. I also believe that assigning the right to sysops is the best default option, as it allows people to indirectly take "sysop actions". In case a wiki sysadmin/community wants it assigned to another user group (or not assigned at all), they just have to remove it, like for any other setting for which we provide a default. Which IMHO is way better than having to remember to assign it to someone.
Comment Actions
Change 468696 had a related patch set uploaded (by Daimona Eaytoy; owner: Daimona Eaytoy):
[mediawiki/extensions/AbuseFilter@master] Rearrange config to provide better experience
Comment Actions
Change 468696 had a related patch set uploaded (by Daimona Eaytoy; owner: Daimona Eaytoy):
[mediawiki/extensions/AbuseFilter@master] Rearrange config to provide better experience
Comment Actions
Change 530349 had a related patch set uploaded (by Daimona Eaytoy; owner: Daimona Eaytoy):
[mediawiki/extensions/AbuseFilter@wmf/1.34.0-wmf.17] Rearrange config to provide better experience
Comment Actions
Change 530349 merged by jenkins-bot:
[mediawiki/extensions/AbuseFilter@wmf/1.34.0-wmf.17] Rearrange config to provide better experience
Comment Actions
Mentioned in SAL (#wikimedia-operations) [2019-08-15T12:14:47Z] <urbanecm@deploy1001> Synchronized wmf-config/: SWAT: 7e95f6d: Update AbuseFilter config to keep the status quo (T191740, T200032, T226987) (duration: 00m 49s)
Comment Actions
Mentioned in SAL (#wikimedia-operations) [2019-08-15T12:16:18Z] <urbanecm@deploy1001> Synchronized php-1.34.0-wmf.17/extensions/AbuseFilter/extension.json: SWAT: rEABFe9422c5c92cb: Rearrange config to provide better experience (T191740, T200032, T226987) (duration: 00m 47s)
Comment Actions
Change 468696 merged by jenkins-bot:
[mediawiki/extensions/AbuseFilter@master] Rearrange config to provide better experience