This template is used on approximately 5,600 pages and changes may be widely noticed. Test changes in the template's /sandbox or /testcases subpages, or in your own user subpage. Consider discussing changes on the talk page before implementing them. |
This template uses Lua: |
Create a list of suspected sockpuppets for an SPI report. Supports an arbitrary number of users. Usernames get wrapped in {{ checkuser}} or {{ checkip}} as applicable, and editor interaction tool links are generated for all listed users.
{{sock list|Example|Example2|2601:1223:5679:BCD:D75:9A71:3A10:B794|2600:8804::/32|8.8.8.8|8.8.4.0/24|127.0.0.1|tools_link=yes}}
{{{tools_link}}}
is a {{
yesno}} parameter determining whether to include the "Tools" link at the end of the sockpuppet list. It is false by default.{{{master}}}
can be set accordingly.{{{hidden}}}
is a {{yesno}} parameter determining whether the list should be hidden (visibility:none;
). This can be useful if one wants to create a list of socks that tools like SPIhelper and spi-tools will pick up, but which won't clutter up the page, perhaps because they've all already been mentioned.{{{remove_master}}}
is a {{yesno}} parameter determining whether to remove the master's name if it shows up in the sock list.{{{template}}}
provides a template to be used in place of {{checkuser}} and {{checkip}}. {{{account_template}}}
overrides just the former; {{{IP_template}}}
overrides just the latter.{{{strike1}}}
, {{{strike2}}}
, etc., are {{yesno}} parameters that can be used to strike out a name in the sock list, based on the number that sock appears at in the template's markup. This is often done if an account is renamed.{{{note1}}}
, {{{note2}}}
, etc., can be used to add a note after a name in the sock list, based on the number that sock appears at in the template's markup. This is often done if a case is moved, to indicate the original mover.To see a few of these parameters in action together, {{sock list|Example|2601:1223:5679:BCD:D75:9A71:3A10:B794|Example2|Example male|2601:1223:5679:BCD:D75:9A71:3A10:B794|2600:8804::/32|8.8.8.8|8.8.4.0/24|127.0.0.1|Example female|tools_link=yes|master=Example|remove_master=yes|account_template=noping2|IP_template=noping|strike3=yes|note3=renamed|note6=({{clerk note}} Original case name)}}
becomes
Note that the {{{striken}}}
and {{{noten}}}
parameters are based on the order specified in the markup. Thus, |strike3=yes
applies to the second rendered item, since the first item in the markup, Example
, is removed by |remove_master=yes
.
This template is used on approximately 5,600 pages and changes may be widely noticed. Test changes in the template's /sandbox or /testcases subpages, or in your own user subpage. Consider discussing changes on the talk page before implementing them. |
This template uses Lua: |
Create a list of suspected sockpuppets for an SPI report. Supports an arbitrary number of users. Usernames get wrapped in {{ checkuser}} or {{ checkip}} as applicable, and editor interaction tool links are generated for all listed users.
{{sock list|Example|Example2|2601:1223:5679:BCD:D75:9A71:3A10:B794|2600:8804::/32|8.8.8.8|8.8.4.0/24|127.0.0.1|tools_link=yes}}
{{{tools_link}}}
is a {{
yesno}} parameter determining whether to include the "Tools" link at the end of the sockpuppet list. It is false by default.{{{master}}}
can be set accordingly.{{{hidden}}}
is a {{yesno}} parameter determining whether the list should be hidden (visibility:none;
). This can be useful if one wants to create a list of socks that tools like SPIhelper and spi-tools will pick up, but which won't clutter up the page, perhaps because they've all already been mentioned.{{{remove_master}}}
is a {{yesno}} parameter determining whether to remove the master's name if it shows up in the sock list.{{{template}}}
provides a template to be used in place of {{checkuser}} and {{checkip}}. {{{account_template}}}
overrides just the former; {{{IP_template}}}
overrides just the latter.{{{strike1}}}
, {{{strike2}}}
, etc., are {{yesno}} parameters that can be used to strike out a name in the sock list, based on the number that sock appears at in the template's markup. This is often done if an account is renamed.{{{note1}}}
, {{{note2}}}
, etc., can be used to add a note after a name in the sock list, based on the number that sock appears at in the template's markup. This is often done if a case is moved, to indicate the original mover.To see a few of these parameters in action together, {{sock list|Example|2601:1223:5679:BCD:D75:9A71:3A10:B794|Example2|Example male|2601:1223:5679:BCD:D75:9A71:3A10:B794|2600:8804::/32|8.8.8.8|8.8.4.0/24|127.0.0.1|Example female|tools_link=yes|master=Example|remove_master=yes|account_template=noping2|IP_template=noping|strike3=yes|note3=renamed|note6=({{clerk note}} Original case name)}}
becomes
Note that the {{{striken}}}
and {{{noten}}}
parameters are based on the order specified in the markup. Thus, |strike3=yes
applies to the second rendered item, since the first item in the markup, Example
, is removed by |remove_master=yes
.