Page MenuHomePhabricator

Block log by abuse filter should link to abuse filter log
Open, MediumPublic

Description

When AbuseFilter blocks a user we can't see the AbuseLog's detail on recentchanges (same goes for block log Special:Log). please add a link to the block's summary about details of the action made causing abuse filter to block the user.
for example here is a log which shows on recent changes

(Block log); 20:39 . . Abuse filter (talk | contribs | block) blocked 91.107.162.250 (talk) with an expiration time of 7 days (account creation disabled) ‎(Blocked by regex:)

it should be like below

(Block log); 20:39 . . Abuse filter (talk | contribs | block) blocked 91.107.162.250 (talk) with an expiration time of 7 days (account creation disabled) ‎(Blocked by regex:) (details)

which details linked to https://en.wikipedia.org/wiki/Special:AbuseLog/####

Event Timeline

Yamaha5 created this task.Jul 3 2016, 9:15 PM
Restricted Application added subscribers: Zppix, Aklapper. · View Herald TranscriptJul 3 2016, 9:15 PM
Yamaha5 updated the task description. (Show Details)Jul 3 2016, 9:22 PM
Ladsgroup renamed this task from feature for blocking by AbuseFilter to Block log by abuse filter should link to abuse filter log.Jul 3 2016, 9:31 PM
Ladsgroup updated the task description. (Show Details)
MarcoAurelio triaged this task as Medium priority.Jul 20 2016, 11:13 AM
MarcoAurelio moved this task from Backlog to Logging on the AbuseFilter board.
MarcoAurelio added a subscriber: MarcoAurelio.
Dalba awarded a token.Aug 8 2016, 8:35 AM
Dalba added a subscriber: Dalba.
dmaza claimed this task.Aug 8 2017, 1:39 AM
TBolliger added a subscriber: TBolliger.

Removed from sprint, requires a major change, so not in scope for this initial stage of development. Back to the backlog.

TBolliger removed dmaza as the assignee of this task.Nov 22 2017, 4:52 PM
TBolliger removed a project: Anti-Harassment.
TBolliger added a subscriber: dmaza.

This will be very difficult: unless you want to guess (which we should avoid), you need to know the logid before executing the block. This all happens in the opposite order, though.

Indeed. And the required change would be too big to only give such a link more. However, there may be a dirty alternative: after having logged to AbuseLog, i.e. when we have the logid, we may run a $dbr->update to the logging table and add the link to log_parameters. However, this isn't a sane way to perform this.