User got renamed however filters modified/created with his old username are still shown with the old username in logs & histories of the extension.
Thanks.
URL: https://es.wikipedia.org/wiki/Especial:AbuseFilter
See Also:
User got renamed however filters modified/created with his old username are still shown with the old username in logs & histories of the extension.
Thanks.
URL: https://es.wikipedia.org/wiki/Especial:AbuseFilter
See Also:
Subject | Repo | Branch | Lines +/- | |
---|---|---|---|---|
Integrate with Renameuser | mediawiki/extensions/AbuseFilter | master | +23 -0 |
The same problem happens with the CodeReview extension. Is this something that could be fixed in both extensions at once?
thogol wrote:
I want to add that a search for the old username does not give any results with the log, despite the fact that the old username does still appear in the log (you get there only by searching for the *new* username which does in fact *not* appear in the log). It's very confusing. :)
Best regards.
This is because user renaming is not a MediaWiki core feature. We use Extension:Renameuser.
Extension:Renameuser provides several hooks for other extensions to register their tables/columns that need updating in case of a rename.
So it is correct that this is a request for the AbuseFilter extension to use those hooks.
Change 145156 had a related patch set uploaded by Legoktm:
Use user id to get a logged in user's name
I agree that the user text needs to be updated from the old username to the new username. Otherwise, viewing the abuse filter log for the new username would just say "No results" or new entries after the rename instead of the entries prior to the rename. We should also make UserCache work globally. Once that happens, please try to merge Change 145156.
While it might not completely fix the problem for global filters, would a hook "onRenameUserSQL" in the style of this patch to CheckUser solve most of this problem?
Given that T167246 is not progressing really, I'm okay with implementing a temporary partial solution as described by @ST47. @Daimona and @matej_suchanek what do you think?
The task to wait for was T188180. But this can work without that for abuse_filter and abuse_filter_history. abuse_filter_log is complicated because of global filters and other issues.
Change 631182 had a related patch set uploaded (by Matěj Suchánek; owner: Matěj Suchánek):
[mediawiki/extensions/AbuseFilter@master] Integrate with Renameuser
Change 631182 merged by jenkins-bot:
[mediawiki/extensions/AbuseFilter@master] Integrate with Renameuser
Just came to report this, but it seems to have been done already
Can existing entries be fixed via script?
I'd say no. The existing entries will be fixed by the actor migration, which is going to require a maintenance script anyway.
The remaining part is blocked on several limitations that cannot be reasonably resolved within the project.
Can the "rename" problem be avoided by having the userid (which doesn't change in renames) be captured in to the AF data, then use that?