Last modified: 2013-07-22 20:25:48 UTC
Created attachment 9271 [details] Screenshot of Special:Contributions Hi. I've blocked an IP on pt.wiki. The block expired on October 8, but, when opening Special:Contributions today, there was still a block notice as if that IP was yet blocked. The IP is http://pt.wikipedia.org/wiki/Especial:Contribui%C3%A7%C3%B5es/189.112.168.139 . The problem seems to be related only with Special:Contributions as it appeared unblocked at block list ( http://pt.wikipedia.org/wiki/Especial:Registo_de_bloqueios ) Note: that IP was reblocked today. Thanks, Teles http://pt.wikipedia.org/wiki/Usu%C3%A1rio:Teles
Maybe related to Bug 31403 ??
(In reply to comment #1) > Maybe related to Bug 31403 ?? Maybe. My complaint is similar with this: http://en.wikipedia.org/w/index.php?diff=454640449 It might be related with autoblocks as this IP has been constantly used by vandalism accounts that were blocked recently. Looks like the most recent IP block log is shown when it is autoblocked. Teles http://pt.wikipedia.org/wiki/Usu%C3%A1rio:Teles
Created attachment 9312 [details] Screenshot of editing interface of blocked user, identifying last entry as an unblock User was blocked and then subsequently unblocked. The user states currently is only able to edit the user talk page and is unable to edit any other pages.
It is still happening and this bug is not fixed: http://pt.wikipedia.org/wiki/Especial:Contribui%C3%A7%C3%B5es/189.52.126.246 It is kind of a breach on privacy policy. I'm not a checkuser, but I know the IP of a blocked account as the IP is autoblocked and blocking notice allows me to relate them (I could link to the account that used this IP, but I won't of course). Teles http://pt.wikipedia.org/wiki/Usu%C3%A1rio:Teles
Is this still a problem after bug 5445 has been fixed with Gerrit change #3841? *** This bug has been marked as a duplicate of bug 3841 ***
Is this still a problem after bug 5445 has been fixed with Gerrit change #3841? *** This bug has been marked as a duplicate of bug 5445 ***
*** This bug has been marked as a duplicate of bug 46457 ***