User talk:Starmoonie

Archives 1

Leave topics signed with "~~~~" or your own personal signature, Thank you.

Notice about the Warning template

Hello fellow administrator. I wanted to make you aware of an upcoming changeover regarding the {{Warning}} template. You can see the discussion of this change here.

Starting now, a new warning template will be available for use. This template is currently available at {{NewWarning}}. However, on April 2, the new warning template will be moved to {{Warning}} and the old warning template will be retired. Please use this transition period to test out the new template before the full changeover. In the period leading up to the changeover, please report any bugs or issues, and offer any suggestions, in the new template discussion

The new template does away with the <reason> parameter of the old template. You can now make your warning more specific by filling in the <type> parameter. Type will automatically load in text depending on the type and the level you select. Additionally, certain types have multiple 'levels', ranging from 1 to 3, with 1 being the least severe, and 3 being the most severe phrasing of the warning message itself. The types are:

• Vandalism (entered as 'vandal#') warns against making non-constructive edits. The 'vandal1' message is the template's default message if no type is entered.
• Blanking pages or sections (entered as 'blank#') warns against removing content from entire pages or sections of pages.
• Removing content (entered as 'remove#') warns against removing useful and accurate content from pages.
• Violating file policy (entered as 'file#') warns users that upload files or images in violation of the Image and File policy.
• Disruptive behavior (entered as 'disrupt') warns users that attack other users, engage in edit warring, etc.
• Sockpuppetry (entered as 'sock') warns users that are suspected of having control over multiple unauthorized accounts.
• Additionally, there is a custom option available if none of the pre-existing types suit your needs. If you choose to use a custom message, the <type> parameter should be set to 'custom' and the optional <custom> parameter will hold your message. If <type> says anything other than 'custom' and the <custom> parameter is filled in, the custom message will not display.

So, to sum it up, the parameters are:

<type>: You should fill this parameter in, unless you're alright with displaying the default, non-specific warning text.

<custom>: Fill this in only if you've filled in 'custom' under the <type> parameter; otherwise, leave this blank.

<sig>: This parameter is mandatory - include your signature here.

<other>: If you want to include additional information to the recipient, you can fill in this parameter. The text you enter will appear below your signature but above the 'boilerplate' message at the bottom of the notification.

One last thing... remember to substitute the template, just as you do when you use {{Warning}}. This is to ensure that any future changes to the template don't alter how it appears on user talk pages.

If you've got any questions about this new warning or its implementations, feel free to drop me a message. -- LostInRiverview ^{talk ~ blog} 04:10, March 19, 2013 (UTC)