Knowledge (XXG)

:High-risk templates - Knowledge (XXG)

Source 📝

232:, pages are cached and template changes are slowly rolled out across the entire encyclopedia. In some cases, pages may have their caches updated before the vandalism is reverted, and these may stick around for a long time even after the vandalism is fixed. This problem scales with the number of transclusions as the time for changes to roll out increases as the number of pages needing updates increases. Some templates like user warnings are substituted instead of transcluded, and when used the source code of the template is inserted directly onto the page. Because these uses do not update when template vandalism is reverted, disruption on substituted templates will stick around until someone finds the use and fixes it manually—making this kind of vandalism harder to clean up. 243:, administrators are given wide latitude to use page protection in order to minimize the unique risks posed by the technical aspects of templates. The technical knowledge required to carry out these attacks is non-trivial, and experience has shown that vandalism to templates is often performed by long-term abusive editors and sleeper accounts. For templates which carry high risk but require frequent maintenance from the general editorial community, lower protection levels such as semi-protection or extended-confirmed protection may be used. For templates that are stable, part of our critical technical infrastructure, or used across thousands of pages, administrators should consider full protection or template protection to enforce 37: 102: 227:
Although template vandalism is usually reverted quickly (often within one minute), the technical aspects of templates create a greater potential for damage than other kinds of vandalism. For templates that are used across hundreds or thousands of articles, any vandalism, no matter how short, could be
223:
For templates and modules that are widely used, the damage caused by bad faith or incorrect edits is uniquely high. The fact that numerous readers would see an edit to these pages provides an incentive to vandalize them and also magnifies the damage done by such an act. There have also been cases
132:
to Knowledge (XXG). If fully protected so that they can only be edited by administrators, or template-protected so that they can only be edited by administrators and template editors, these pages should be edited cautiously, and consensus should be established for any changes that might be
380: 164:
There are generally no fixed criteria, and no fixed number of transclusions, that are used to decide whether a template or module is high-risk; each page is considered separately. If a template or module relates to a
443: 133:
controversial. If semi-protected or extended-confirmed protected, templates and modules may be edited by any established user, but users should ensure there is consensus for their edits and avoid edit wars.
437: 385: 375: 194: 319:
to protected templates, which displays a small padlock in the top right corner and categorizes the template as a protected template. Only manually add
481: 155:
It is substituted extremely frequently by multiple users on an ongoing basis (for example, templates used to warn users about inappropriate editing).
471: 366:
This process is not necessary for Lua modules, as the documentation from the module's /doc subpage is automatically shown on the main module page.
166: 44: 476: 60: 449: 294: 176: 409: 281:
If the template breaks for even a minute while you are making incremental improvements, the breakage may be seen by many readers.
458:– Describes the template editor user right, and has some notes on the level of discussion required for different types of edits. 121: 424:– To request that other editors update a page, for users that are not logged in or are too new to edit a semi-protected page. 117: 399: 201:
identified a rough consensus to permanently extended-confirmed protect templates with roughly 2500 to 5000 transclusions.
110:
High-risk templates and Lua modules may be edit protected. Edits to such pages should be made only after careful testing.
52: 419: 236: 455: 274:
For templates with a very high number of transclusions, minimizing the number of edits to the template is important:
235:
In all cases, page protection minimizes the risk posed by bad faith or technically deficient edits to templates (see
256:
It is good practice to make edits on the template's /sandbox page rather than directly to the high-risk template.
376:
Knowledge (XXG):Village pump (proposals)/Archive 145 § A proposal to permanently semi-protect the Template space
278:
Each edit to the template will create server load as it updates the cached wikicode of thousands of other pages.
197:
identified rough consensus to permanently semiprotect templates with at least around 200–250 transclusions, and
229: 311:
page, so that non-admins and IP-users can edit the documentation and categories. It also automatically adds
198: 330: 302: 240: 262:
Test your new /sandbox code and make sure it is bug-free. Check the /testcases page to assist with this.
69: 56: 322: 314: 381:
Knowledge (XXG):Requests for comment/Extended confirmed protection policy 2 § High-risk templates
429: 224:
where well-meaning editors introduced an error to a template that broke millions of pages.
173: 125: 414:– Placed on a talk page to request an edit of the corresponding template protected page. 216:
To prevent high server load from unnecessary extra edits to highly transcluded templates
17: 386:
Knowledge (XXG):Village pump (proposals)/Archive 184 § Should we use ECP on templates?
465: 404:– Placed on a talk page to request an edit of the corresponding fully protected page. 247:
through edit requests which helps prevent accidental bugs and deliberate attacks.
358:<!-- Categories go on the /doc subpage, and interwikis go on Wikidata. --: --> 446:– An auto-generated feed listing the most transcluded templates sorted by count. 244: 169:, that would strengthen any arguments in favor of its preemptive protection. 146: 219:
To reduce chances of accidental breakage by inexperienced template editors
141:
The most common reasons a template or module is considered high-risk are:
438:
Knowledge (XXG):List of indefinitely protected pages § High use templates
444:
Knowledge (XXG):Database reports/Templates transcluded on the most pages
259:
If needed, get consensus for your changes on the template's talk page.
452:– A page which cascade-protects many widely used templates and files. 209:
The main reasons for restricting access to high-risk templates are:
186:
extended-confirmed protects pages with over 2,500 transclusions, and
338:
The bottom of protected templates should usually look like this:
145:
It is used in a permanently highly visible location (such as the
228:
seen by many readers across the entire encyclopedia. To prevent
440:– An incomplete list of templates protected per this guideline. 434:– Placed on a template to indicate it is a high-risk template. 285:
Please do the majority of your edits in the /sandbox instead.
96: 31: 299:
Semi- and fully-protected templates should normally have the
55:
may apply. Substantive edits to this page should reflect
128:
that have been identified by the community as being of
84: 77: 265:
Deploy your /sandbox code to the template in one edit.
183:
template-protects pages with over 5,000 transclusions,
120:, page protection may be indefinitely applied to all 152:
It is transcluded into a very large number of pages.
270:Minimizing edits to highly transcluded templates 189:semi-protects pages with over 250 transclusions. 27:Editing guideline related to template protection 43:This page documents an English Knowledge (XXG) 8: 343:<!--Last line of the template code--: --> 307:template. It loads the usually unprotected 251:The correct way to edit high-risk templates 51:Editors should generally follow it, though 241:policy prohibiting preemptive protection 450:Knowledge (XXG):Cascade-protected items 327:to protected templates that don't use 295:Knowledge (XXG):Template documentation 7: 482:Knowledge (XXG) template guidelines 472:Knowledge (XXG) editing guidelines 59:. When in doubt, discuss first on 25: 100: 35: 477:Knowledge (XXG) page protection 456:Knowledge (XXG):Template editor 1: 335:(mostly the stub templates). 239:). In contrast to our usual 237:principle of least privilege 167:biography of a living person 498: 292: 124:, template redirects, and 67: 61:this guideline's talk page 289:Documentation and padlock 230:denial of service attacks 340: 108:This page in a nutshell: 18:Knowledge (XXG):HIGHRISK 410:Edit template-protected 400:Edit fully-protected 370:Relevant discussions 213:To prevent vandalism 420:Edit semi-protected 361:</noinclude: --> 346:<noinclude: --> 118:protection policy 114: 113: 95: 94: 45:editing guideline 16:(Redirected from 489: 433: 423: 413: 403: 362: 359: 356: 353: 350: 347: 344: 334: 326: 318: 310: 306: 104: 103: 97: 87: 80: 39: 38: 32: 21: 497: 496: 492: 491: 490: 488: 487: 486: 462: 461: 427: 417: 407: 397: 394: 372: 364: 363: 360: 357: 354: 351: 348: 345: 342: 328: 320: 312: 308: 300: 297: 291: 272: 253: 207: 162: 139: 101: 91: 90: 83: 76: 72: 64: 36: 28: 23: 22: 15: 12: 11: 5: 495: 493: 485: 484: 479: 474: 464: 463: 460: 459: 453: 447: 441: 435: 425: 415: 405: 393: 390: 389: 388: 383: 378: 371: 368: 341: 290: 287: 283: 282: 279: 271: 268: 267: 266: 263: 260: 257: 252: 249: 221: 220: 217: 214: 206: 203: 191: 190: 187: 184: 161: 158: 157: 156: 153: 150: 138: 137:Common reasons 135: 116:Following the 112: 111: 105: 93: 92: 89: 88: 81: 73: 68: 65: 50: 49: 40: 26: 24: 14: 13: 10: 9: 6: 4: 3: 2: 494: 483: 480: 478: 475: 473: 470: 469: 467: 457: 454: 451: 448: 445: 442: 439: 436: 431: 426: 421: 416: 411: 406: 401: 396: 395: 391: 387: 384: 382: 379: 377: 374: 373: 369: 367: 352:Documentation 339: 336: 332: 331:Documentation 324: 316: 304: 303:Documentation 296: 288: 286: 280: 277: 276: 275: 269: 264: 261: 258: 255: 254: 250: 248: 246: 242: 238: 233: 231: 225: 218: 215: 212: 211: 210: 204: 202: 200: 196: 188: 185: 182: 181: 180: 178: 177:automatically 175: 170: 168: 159: 154: 151: 148: 144: 143: 142: 136: 134: 131: 127: 123: 119: 109: 106: 99: 98: 86: 82: 79: 75: 74: 71: 66: 62: 58: 54: 48: 46: 41: 34: 33: 30: 19: 365: 337: 298: 284: 273: 234: 226: 222: 208: 192: 171: 163: 140: 129: 115: 107: 42: 29: 323:pp-template 315:pp-template 293:Main page: 245:code review 126:Lua modules 85:WP:HIGHRISK 466:Categories 199:a 2021 RfC 172:Note that 53:exceptions 205:Rationale 147:Main page 130:high risk 122:templates 70:Shortcuts 57:consensus 430:High-use 392:See also 195:2018 RfC 160:Criteria 78:WP:HRT 174:a bot 309:/doc 468:: 432:}} 428:{{ 422:}} 418:{{ 412:}} 408:{{ 402:}} 398:{{ 355:}} 349:{{ 333:}} 329:{{ 325:}} 321:{{ 317:}} 313:{{ 305:}} 301:{{ 193:A 179:: 149:) 63:. 47:. 20:)

Index

Knowledge (XXG):HIGHRISK
editing guideline
exceptions
consensus
this guideline's talk page
Shortcuts
WP:HRT
WP:HIGHRISK
protection policy
templates
Lua modules
Main page
biography of a living person
a bot
automatically
2018 RfC
a 2021 RfC
denial of service attacks
principle of least privilege
policy prohibiting preemptive protection
code review
Knowledge (XXG):Template documentation
Documentation
pp-template
pp-template
Documentation
Knowledge (XXG):Village pump (proposals)/Archive 145 § A proposal to permanently semi-protect the Template space
Knowledge (XXG):Requests for comment/Extended confirmed protection policy 2 § High-risk templates
Knowledge (XXG):Village pump (proposals)/Archive 184 § Should we use ECP on templates?
Edit fully-protected

Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.