MediaWiki talk:Checkuser-toollinks

EP[edit]

This edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request.

‹ The template Edit fully-protected is being considered for merging. ›

ip2location is working again and it is more accurate than the new "geolocate" link. I would like that it haves it back. ~~EBE123~~ ^talk_Contribs 14:15, 19 June 2011 (UTC)[reply]

Done — Martin (MSGJ · talk) 12:56, 20 June 2011 (UTC)[reply]

RDNS[edit]

This edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request.

‹ The template Edit fully-protected is being considered for merging. ›

Not working. It's a parked page. Charitwo ^(talk) 18:43, 12 July 2011 (UTC)[reply]

Removed for now. — Martin (MSGJ · talk) 12:41, 13 July 2011 (UTC)[reply]

Protected edit request on 22 March 2019[edit]

This edit request to MediaWiki:Checkuser-toollinks, MediaWiki:Checkuser-toollinks/en-ca and MediaWiki:Checkuser-toollinks/en-gb has been answered. Set the |answered= or |ans= parameter to no to reactivate your request.

‹ The template Edit fully-protected is being considered for merging. ›

Please replace

[{{fullurl:Special:CheckUserLog|cuSearchType=target&cuSearch=$1}} checks] •

with

<span class="checkuser-show">[{{fullurl:Special:CheckUserLog|cuSearchType=target&cuSearch=$1}} checks] • </span>

to hide the link that requires checkuser rights from non-check users.

Thanks, --DannyS712 (talk) 09:11, 22 March 2019 (UTC)[reply]

@DannyS712: Um, as far as I know this entire message is only available through the (restricted) CU special pages. It seems to me the only effect this change will have is to make the link not visible while looking at this message page, and that doesn't seem particularly helpful. ? -- zzuuzz ^(talk) 17:50, 22 March 2019 (UTC)[reply]

@Zzuuzz: Oh. I didn't know that. Feel free to decline if there are no other uses --DannyS712 (talk) 17:58, 22 March 2019 (UTC)[reply]

OK, until someone presents any other usage. -- zzuuzz ^(talk) 18:03, 22 March 2019 (UTC)[reply]