Meta | Commons | Wikibooks | Wikiquote | Wikisource | Wiktionary | Wikivoyage | Wikidata | Deutsch | Français | Nederlands

This message on this site, depending on the user-specified interface language:

  • en (English):
Technical instructions and special cases
Instructions

By default, protection lasts indefinitely. To specify an expiry, enter a length of time (e.g. "31 hours", "5 days" or "1 week") or an expiration date (e.g. "1 November 2019") in GNU standard format. Please update the protection templates on the page after changing the protection level.

  • Avoid non-integer values, such as "2.37 weeks" or "1.84 days"; the MediaWiki software might not format them correctly.
  • Move protection and edit protection can be applied separately or together, and each set for different lengths of time.
    • This allows pages to be protected from editing for a definite period of time while move protection can remain indefinitely.
  • Pending changes protection is unavailable for use on talk pages or anywhere within the user space.
  • The confirmed or autoconfirmed user right is required in order for accounts to move any pages at all.
  • All pages that are currently edit protected are publicly visible at Special:ProtectedPages.
  • All pages that are currently create protected (salted) are publicly visible at Special:ProtectedTitles.
  • All pages that are currently pending changes protected are publicly visible at Special:StablePages.
  • af (Afrikaans / Afrikaans): U kan die veiligheidsvlak vir blad $1 hier bekyk of verander.
  • ar (Arabic / العربية): يمكنك هنا أن تعرض وتغير مستوى الحماية للصفحة $1.
  • bg (Bulgarian / Български): Тук можете да прегледате и промените нивото на защита на страницата $1.
  • bn (Bengali / বাংলা): $1 পাতাটির জন্য সুরক্ষার স্তর আপনি এখানে দেখতে ও পরিবর্তন করতে পারেন।
  • da (Danish / Dansk): Her kan beskyttelsesstatus for siden $1 ses og ændres.
  • de (German / Deutsch): Hier kannst du den Schutzstatus der Seite „$1“ einsehen und ändern.
  • eo (Esperanto / Esperanto): Vi povas ĉi tie vidi kaj ŝanĝi la protektnivelon de la paĝo $1.
  • es (Spanish / Español):
    Puedes visualizar y modificar el nivel de protección de $1. Por favor, asegúrate de que sigues las políticas de protección de páginas.
  • eu (Basque / Euskara): «$1» orriaren babes maila ikusi eta aldatu egin beharko zenuke.
  • fr (French / Français): Ici vous pouvez consulter et modifier le niveau de protection de la page $1.
  • fy (West Frisian / Frysk): Hjir kin jo it nivo fan skoatteljen sjen en oanpasse foar de side $1.
  • it (Italian / Italiano): Questo modulo consente di vedere e modificare il livello di protezione per la pagina $1.
  • la (Latin / Latina): Hic tibi licet protectiones legere et mutare paginae $1.
  • li (Limburgian / Limburgs): Hie kins te 't beveiligingsniveau veur de pagina $1 bekieke en verangere.
  • nl (Dutch / Nederlands): Hier kunt u het beveiligingsniveau voor de pagina $1 bekijken en wijzigen.
  • no (Norwegian / ‪Norsk (bokmål)‬): Here you may view and change the protection level for the page $1.
  • pl (Polish / Polski): Możesz tu sprawdzić i zmienić stopień zabezpieczenia strony $1.
  • pt (Portuguese / Português): Pode ver e alterar aqui o nível de proteção da página $1.
  • ru (Russian / Русский): Вы можете просмотреть и изменить уровень защиты для страницы $1.
  • sv (Swedish / Svenska): Här kan du se och ändra skrivskyddsnivån av sidan $1.

Pages in the MediaWiki namespace regarding this message

Why the "Page $1"?Edit

Why does the protection infobox contain the phrase "...for the page $1" (Wikimarkup '''''<nowiki>$1</nowiki>''''')? It has been that way since the page was created in 2007. Are the nowiki tags an error that stop the $1 from being substituted? Guy Macon (talk) 12:50, 16 May 2011 (UTC)

The $1 is a placeholder, and is replaced by the actual page title when the message is displayed on the protection interface. E.g., on this page the interface reads "You may view and change the protection level here for the page MediaWiki talk:Protect-text". Not sure whether the nowiki tags are actually required (don't known at which point of parsing the placeholder is substituted), but they don't hurt. Amalthea 13:52, 16 May 2011 (UTC)

Thanks! Guy Macon (talk) 14:42, 16 May 2011 (UTC)

Confirm protection dropdownsEdit

I realize this is almost certainly the wrong place, but I'm leaving this here because for the life of me I can't find the correct page. In the "Edit" and "Move" dropdown boxes in the "Confirm protection" area of the protection MediaWiki page, the top selection for both is currently "Allow only template editors and admins". This seems counter-intuitive to me; I think it is more logical for the topmost option to be no protection at all, as has traditionally been the case. So, if someone with the proper know-how would be so kind - and provided it won't break anything - could you please move "Allow only template editors and admins" down to the third or fourth slots in both boxes. Thanks. --Bongwarrior (talk) 01:35, 16 August 2014 (UTC)

I don't think that order is being driven from MediaWiki, but from the source. Anomie or coren were involved with the code on this, pinging. — xaosflux Talk 02:00, 16 August 2014 (UTC)
The order is actually coming from the configuration, $wgRestrictionLevels. I'll follow up with a bug and patch. Anomie 02:21, 16 August 2014 (UTC)
Thank you both for the quick responses. --Bongwarrior (talk) 02:25, 16 August 2014 (UTC)
Anomie's proposed patch is [1] and is being currently opposed by odder, Steinsplitter and Ricordisamoa. Guys, can any of you explain that, because I honestly don't understand? Matma Rex talk 11:26, 16 August 2014 (UTC)
@Matma Rex: I don't think that is required. Why don't you just continue calling the three of us fucking retards? That's helpful, thanks! odder (talk) 11:28, 16 August 2014 (UTC)
Ricordisamoa has always been a nice person in my experience and I'd never say such a thing about them. Matma Rex talk 11:39, 16 August 2014 (UTC)
@Matma Rex: Fine. If you consider myself and @Steinsplitter fucking retards, why are you pinging us and asking for information? It is clear that you don't really want it, so why bother. odder (talk) 11:47, 16 August 2014 (UTC)
  • Just wanted to note that this has been fixed. Thanks again for the help. --Bongwarrior (talk) 16:31, 20 August 2014 (UTC)
    • The drama about the patch was that it mentioned the Superprotect level, however this patch had nothing to do with that other than making sure if it appeared it would be at the bottom of the list. — xaosflux Talk 01:42, 21 August 2014 (UTC)

Edit requestEdit

The page links to Special:ProtectedTitles when it should link to Special:ProtectedPages, which is the actual protected pages list.Jo-Jo Eumerus (talk, contributions) 14:37, 13 January 2016 (UTC)

  Donexaosflux Talk 15:09, 13 January 2016 (UTC)
Actually, it applies to both create-protect, and normal protect - adding both links. — xaosflux Talk 15:10, 13 January 2016 (UTC)

Using a different version of the lock image?Edit

Looking at the new full protection lock, I'm not sure the is a good fit for our use case here. My understanding is that we used the old full protection lock to represent protection generally, not specifically full protection. Given that the new one has a large "F" on it which, in my estimation, makes it look out of place in this context, are there any opinions on using one of the below images to represent protection generally instead?

I personally like the keyhole version (disclaimer: I made the keyhole one from the base SVG) and wanted to see if there were opinions either way. Best, Mifter (talk) 04:26, 15 November 2018 (UTC)

Yeah — I replaced it to match, but I agree having a good generic lock for "protected" or "unprotected" would be good. I have no strong opinion. Courtesy ping XYZtSpace. ~ Amory (utc) 15:03, 15 November 2018 (UTC)
  • Agree, for this specific message a more generic lock is better - since it is on the message about setting the level. OK with either one, image should be locally uploaded then upload protected. — xaosflux Talk 15:58, 15 November 2018 (UTC)
  • Seeing no opposition (or further input) despite the {{sudo}} tag, I'm willing to make this (relatively minor) change — let's say the keyhole. Mifter, do you want to upload per Xaosflux' request? Not nearly as high-visibility as the others, but worth protecting nonetheless. ~ Amory (utc) 16:48, 19 November 2018 (UTC)
Amorymeltzer -   Done -Mifter (talk) 00:28, 20 November 2018 (UTC)
  Donexaosflux Talk 01:02, 20 November 2018 (UTC)
Return to "Protect-text" page.