Template:Checkuser is permanently protected from editing because it is a heavily used or highly visible template. Substantial changes should be proposed here first. If the proposal is uncontroversial or has been discussed and is supported by consensus, editors may use ((edit template-protected)) to notify an administrator or template editor to make the requested edit. Usually, any contributor may edit the template's documentation to add usage notes or categories. Any contributor may edit the template's sandbox. Functionality of the template can be checked using test cases.

Okay, so let's discuss this! Apparently removing 1,655 bytes of code from this template directly and calling it from a sub-template which is 1,937 bytes (282 byte difference) is causing issues on large archives. What is this sub template suppose to improve? Why does it need to be a sub-template increasing expansion depth? Technical 13 (talk) 16:23, 21 November 2013 (UTC)Reply[reply]

• A description of what the template is used for would not go amiss either. Is this for listing a user in a sockpuppet report, or specifically requesting somebody compares IP addresses and user agents? Ritchie333 ^{(talk) (cont)} 14:08, 24 December 2013 (UTC)Reply[reply]

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

Please re-do Special:diff/758902751, following the discussion at WT:Notifications#Checkuser and admin questions. Burninthruthesky (talk) 06:50, 13 April 2017 (UTC)Reply[reply]

Done – Train2104 (t • c) 15:34, 13 April 2017 (UTC)Reply[reply]

This will help us pick up cross language issues. More and more common with undisclosed paid editors. Example here[1] Doc James (talk · contribs · email) 08:53, 23 November 2017 (UTC)Reply[reply]

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

This template interprets a pair of apostrophes escaped as '' ('') as italic markup. This really happens; see Wikipedia:Sockpuppet investigations/T*w^E.r''*A;t*?/Archive, which includes the line

: ((checkuser|1=T*w^E.r&#39;&#39;*A;t*?))<br>((SPIold))

and this line is causing a listing at Lint errors: Unclosed quote in heading (namespace=Wikipedia) Anomalocaris (talk) 10:42, 8 February 2018 (UTC)Reply[reply]

 Not done: it's not clear what changes you want to be made. Please mention the specific changes in a "change X to Y" format and provide a reliable source if appropriate. Also, the issue is with ((SPIpriorcases)), not ((Checkuser)) – the apostrophes are not escaped there due to the use of ((PAGENAME)). — JJMC89 (T·C) 15:27, 8 February 2018 (UTC)Reply[reply]

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

Please update this template as shown below, to add some other useful features to it:

<span class="plainlinks">[[User:(({User|(({1|Example))))))|(({User|(({1|Example))))))]] ([[User talk:(({User|(({1|Example))))))|talk]]<sup><big>[((fullurl:User talk:(({1|Example))}|action=edit))&section=new <font color="grey">+</font>]</big></sup> ((middot)) Contribs: <small>[[Special:Contributions/(({User|(({1|Example))))))|local]] / [[Special:DeletedContributions/(({User|(({1|Example))))))|deleted]] / <span class="plainlinks">[https://tools.wmflabs.org/quentinv57-tools/tools/globalcontribs.php?onlylastdays=1&nbdays=90&username=((urlencode:(({User|(({1|Example)))))))) global]</span></small> ((middot)) Logs: <small>[((fullurl:Special:Log/block|page=((urlencode:User:(({1))))} block] / [((fullurl:Special:AbuseLog|wpSearchUser=((urlencode:(({User|(({1|Example)))))))))) abuse] /  [((fullurl:Special:Log|user=((urlencode:(({User|(({1|Example)))))))))) other]</small> ((middot)) [https://meta.wikimedia.org/wiki/Special:CentralAuth/((urlencode:(({User|(({1|Example)))))))) CA] ((middot)) [https://tools.wmflabs.org/dewkin/((urlencode:((#invoke:String|replace|(({1|Example))}| |_))))))@enwiki DEWKIN] ((middot)) [[Special:Block/(({User|(({1|Example))))))|block user]] ((middot)) CU: [((fullurl:Special:CheckUser|user=((urlencode:(({User|(({1|Example)))))))))) check] / [[Special:CheckUserLog/(({User|(({1|Example))))))|log]])</span>((#ifeq:((NAMESPACE))|User talk|<!-- redundant to noindex user talk -->|__NOINDEX__))<noinclude>((#ifeq:((SUBPAGENAME))|sandbox||
((documentation))
))</noinclude>

The new output will be like this:

Example (talk⁺  · Contribs: local / deleted / global  · Logs: block / abuse / other  · CA  · DEWKIN  · block user  · CU: check / log)

Thanks! huji—TALK 22:58, 25 February 2018 (UTC)Reply[reply]

 Not done: please establish a consensus for this alteration before using the ((edit template-protected)) template. Certainly looks like it could be useful, but there would need to be a consensus for this change. You'd probably want to ask those who work at SPI what they think of the change. Galobtter (pingó mió) 05:07, 26 February 2018 (UTC)Reply[reply]

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

the template should have a "block user" link in the toolbar so a sysop/checkuser can block them quickly using the link in the toolbar instead of going to the sockpuppet/sockpuppeter's userpage and then clicking "block user" in the toolbox on the userpage, a block user is usually needed. 46.227.72.88 (talk) 12:54, 20 May 2018 (UTC)Reply[reply]

There is already block user link, but it is only shown to sysops. Galobtter (pingó mió) 13:03, 20 May 2018 (UTC)Reply[reply]

@Galobetter: ok 46.227.72.88 (talk) 14:54, 20 May 2018 (UTC)Reply[reply]

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

Please replace with the current sandbox version (dif). This would:

1. Hide the links to perform checkuser and view the checkuser log from non-check users
2. Remove the check to only add __NOINDEX__ on non-user-talk pages, since there is no inherent problem with adding noindex, and it adds an unneeded invocation of parser functions
3. Show the documentation when looking at the sandbox - don't see a reason to hide it, its useful and helps with understanding the template.

Thanks, --DannyS712 (talk) 17:33, 25 March 2019 (UTC)Reply[reply]

 Done - FlightTime (open channel) 20:05, 25 March 2019 (UTC)Reply[reply]

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

Please replace the following code (which is at the very beginning):

<includeonly>((#if:(({User|(({1|))))))||[[Category:Checkuser with no specified user]]))</includeonly><span class="plainlinks cuEntry">((noping|(({User|(({1|Example))))))))

with this code:

<includeonly>((#if:(({User|(({1|))))))||[[Category:Checkuser with no specified user]]))</includeonly><span class="plainlinks cuEntry">((no ping|(({User|(({1|Example))))))))

This is simply to avoid using a redirect on this template and on the other pages transcluding it.

(See WP:NOTBROKEN, which includes the following: "In other namespaces, particularly the template and portal namespaces in which subpages are common, any link or transclusion to a former page title that has become a redirect following a page move should be updated to the new title for naming consistency.") Jdaloner (talk) 08:11, 1 August 2020 (UTC)Reply[reply]

 Done Sceptre (talk) 09:46, 1 August 2020 (UTC)Reply[reply]

See Wikipedia:Sockpuppet investigations/Терентьев Константин Викторович, "Шериф". If you click on the "CheckUser" link for the master, the "IP address or username" field is filled with "Терентьев Константин Викторович, &", but the "Reason" field correctly gets "Терентьев Константин Викторович, "Шериф" from Wikipedia:Sockpuppet investigations/Терентьев Константин Викторович, "Шериф"". Smells like some urlencode operation not being done properly. -- RoySmith (talk) 17:11, 23 December 2021 (UTC)Reply[reply]

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

Please replace all content of this template with the following:

((#invoke:Checkuser|user<noinclude>|Example</noinclude>))<noinclude>
((doc))
</noinclude>

Courtesy ping to @Pppery. Thank you. NguoiDungKhongDinhDanh 13:39, 26 June 2022 (UTC)Reply[reply]

 Done. P.I. Ellsworth , ed. ^put'r there 05:52, 11 July 2022 (UTC)Reply[reply]