Template talk:Protected page text/Archive 1

Archive 1

Protected edit request on 23 January 2014

Please modify this system message by changing:

| protection-message = This page is currently [[Wikipedia:Protection policy#Full protection|protected]] and can be edited only by [[Wikipedia:Administrators|administrators]].

to:

| protection-message = This page is currently {{#ifexist:{{FULLPAGENAME}}|[[Wikipedia:Protection policy#Full protection|protected]]|[[Wikipedia:Protection policy#Create protection|salted]]}} and can only be {{#ifexist:{{FULLPAGENAME}}|edited|created}} by [[Wikipedia:Administrators|administrators]].

So that the user attempting to create a salted page will know why they are seeing that message. Thank you. Technical 13 (talk) 22:13, 23 January 2014 (UTC)

What about "protected from creation" instead of "salted"? Jackmcbarn (talk) 17:54, 24 January 2014 (UTC)

I'm fine with that, it's a linked word back to the policy, and both terms are accurate. Technical 13 (talk) 18:09, 24 January 2014 (UTC)

@Technical 13 and Jackmcbarn: If we're going to make this message display better custom values for creation protection, I'd prefer a solution that works for all protection levels. Pages can also be create-protected with semi-protection or template protection (although template protection shouldn't be used for salting), so we should make it work the same way for those as it does for full protection. What would we want to do with the bulleted suggestions in the case of salting? At the moment they aren't displayed for full protection, but they are displayed for semi- and template protection. Also, I think it would be best to put the #ifexist parser function(s) in the main {{Protected page text}} and create new parameters for edit protection messages and create-protection messages, rather than cluttering the subtemplates with #ifexist calls. I'm deactivating the edit request for now while we work this out. — Mr. Stradivarius ^{♪ talk ♪} 14:45, 28 January 2014 (UTC)

Protected edit request on 7 April 2014

Change this:

| protection-message = This page is currently protected and can be edited only by Template editors and administrators.

to this:

| protection-message = This page is currently protected and can be edited only by template editors and administrators.

In other words, decapitalize the first 't' in 'template editors'. UpEpSilon (talk) 11:29, 7 April 2014 (UTC)

Done — Mr. Stradivarius ^{♪ talk ♪} 12:28, 7 April 2014 (UTC)

Protected edit request on 20 August 2014

I propose that this template be changed to (or Template:Test-mode used) Edited 01:39, 31 August 2014 (UTC) — Gdfusion 01:20, 20 August 2014 (UTC) — continues after insertion below

Large amount of template content moved to Template:Protected page text/sandbox. Jackmcbarn (talk) 01:50, 31 August 2014 (UTC)

(I copied this from User:Gdfusion/Sandbox/ppt)

• This will change a couple of things. First of all, on a protected or semi-protected talk page, it will remove the edit request button, because as it is currently, the edit request button fails on those pages because it tries to edit the talk page itself, which is protected. See Special:Permalink/621993248 for a preview of how that would work.
• Secondly, let's say user A wants to contact user B, but user B's talk page is protected, so user A can't leave a message on user B's talk page. Then, when user A tries to edit user B's talk page but fails, a new button will appear. This button will leave a message on user A's talk page, notifying user B. See User talk:Gdfusion/Sandbox for an example on how that would work.

I also propose that the template currently located at User:Gdfusion/Sandbox/contact_notify (which is transcluded into the edit I proposed above) be moved to a subpage of this page, in order to minimize cross-namespace transclusions.

Edit: User:Gdfusion/Sandbox/ping_talk_template should also probably be moved to a subpage of this page.

I give credit to Xaosflux, who initially suggested changing this template.

Sorry, this was really hard to explain. Please ask if you need clarification. --gdfusion (talk|contrib) 01:20, 20 August 2014 (UTC)

I endorse this change request, however would like it to sit for a couple of days for anyone to perform review and/or feedback. Sub page suggestion (protected) is: Template:Protected page text/semi/user_talk preload. Gdfusion, please reactivate the protected edit request in a couple of days to put this back in the queue. Good Work! — xaosflux ^Talk 01:37, 20 August 2014 (UTC)

I'll reactivate this request in a few days. Thanks for the support, Xaosflux :) --gdfusion (talk|contrib) 01:59, 20 August 2014 (UTC)

Using test-mode in the interface isn't a good idea. For the change itself, you definitely need to not have {{User:Gdfusion/Sandbox/contact notify}} in this (you should probably just incorporate it into this template, instead of making it its own template). Also, checking #ifeq: Template talk | Template talk and {{#ifeq: Template talk | User talk is redundant. The #ifexist check is unnecessary, and you should add another check to make sure they're on the root talk page and not a subpage (like an archive). Deactivating for now until these things are fixed. (Also, I've put your proposed version in the template's sandbox; please put your fixed version there instead of here.) Jackmcbarn (talk) 01:50, 31 August 2014 (UTC)

Thanks for the feedback.

• Put button into template rather than transclude:  Done. The button itself, though, still needs another page for the preload. Can it be moved into a subpage of this page?
• #ifexist check:  Done. This was initially to check if such a user existed, but I realized that a user doesn't have to have a talk page to exist.
• You're right obviously that normally having both {{#ifeq: {{NAMESPACE}} | {{TALKSPACE}}}} and {{#ifeq: {{NAMESPACE}} | User talk}} is redundant, but if you look at the way it's set up, there's a condition which executes when {{NAMESPACE}} != {{TALKSPACE}} (this is the thing that the edit request button shows up only if talk page isn't the one that's protected). This is my fault because the bracket spacing was initially really bad (bad coding practice). It could just as easily go outside the brackets, of course, but I think this way keeps it more organized.
• Adding a check to make sure they're on the root page:  Done. I initially set it up so that it would work if a subpage is protected and still ping the right user, but now I realize that just because the subpage is protected, the base user talk page might not necessarily be protected. —gdfusion (talk|contrib) 04:41, 31 August 2014 (UTC)

I think there's some mismatched and/or misplaced braces right now. I'll have time to fix them myself later, but if you want, you can fix them now. Jackmcbarn (talk) 14:09, 31 August 2014 (UTC)

Really? They are almost exactly the same as before —gdfusion (talk|contrib) 16:48, 31 August 2014 (UTC)

Protected edit request on 29 August 2014

On Template:Protected page text/semi, please replace the existing call to {{protected page text}} with this one:

{{protected page text
| image = Padlock-silver.svg
| protection-message = This page is currently semi-protected so that only established [[Wikipedia:Why create an account?|registered users]] can {{{2}}} it.
| suggestions = yes
| protection-reason = While most articles can be edited by anyone, [[Wikipedia:Protection policy#Semi-protection|semi-protection]] is sometimes necessary to prevent [[Wikipedia:Vandalism|vandalism]] to popular pages.
| login-message = yes
| who-can-edit = An [[Wikipedia:User access levels#Autoconfirmed users|established user]]
| request-type = semi
| attempted-action = {{{2}}}
}}

On Template:Protected page text/template, please replace the existing call to {{protected page text}} with this one:

{{protected page text
| image = Padlock-pink.svg
| protection-message = This page is currently [[Wikipedia:Protection policy#Template protection|protected]] so that only [[Wikipedia:Template editors|template editors]] and [[Wikipedia:Administrators|administrators]] can {{{2}}} it.
| suggestions = {{#ifexist: {{FULLPAGENAME}} | yes}}
| protection-reason = Some [[Wikipedia:Template messages|templates]] and site interface pages are permanently [[Wikipedia:Protection policy#Template protection|protected]] due to visibility. Most templates can be edited by anyone.
| template-links = yes
| who-can-edit = An [[Wikipedia:Administrators|administrator]] or [[Wikipedia:Template editor|template editor]]
| request-type = template
| attempted-action = {{{2}}}
}}

On Template:Protected page text/full, please replace the existing call to {{protected page text}} with this one:

{{protected page text
| image = Padlock{{#switch:{{{2}}}|move=-olive|upload=-purple|create=-skyblue}}.svg
| protection-message = This page is currently [[Wikipedia:Protection policy#{{#switch:{{{2}}}|move=Move|upload=Upload|create=Creation|Full}} protection|protected]] so that only [[Wikipedia:Administrators|administrators]] can {{{2}}} it.
| suggestions = {{#ifexist: {{FULLPAGENAME}} | yes}}
| protection-reason = Some [[Wikipedia:Template messages|templates]] and site interface pages are permanently [[Wikipedia:Protection policy#Full protection|protected]] due to visibility. Occasionally, articles are temporarily protected because of [[Wikipedia:Edit war|editing disputes]]. Most articles can be edited by anyone.
| main-page-links = yes
| template-links = yes
| who-can-edit = An [[Wikipedia:Administrators|administrator]]
| request-type = full
| attempted-action = {{{2}}}
}}

Jackmcbarn (talk) 14:50, 29 August 2014 (UTC)

Done — Mr. Stradivarius ^{♪ talk ♪} 14:59, 29 August 2014 (UTC)

Protected edit request on 12 March 2016

I found an error in the message that appears when unauthorized users try to rename move-protected pages (e.g. Test). The protection log link under the second bullet point currently links to https://wiki.riteme.site/w/index.php?title=Special:Log&type=protect&page=Special:MovePage/Test instead of https://wiki.riteme.site/w/index.php?title=Special:Log&type=protect&page=Test -- SLV100 (talk) 03:13, 12 March 2016 (UTC)

The problem is that when attempting to move a page (e.g. Test) the message is being viewed from Special:MovePage/Test and not from Test, so {{FULLPAGENAMEE}} evaluates to Special:MovePage/Test instead of Test. I think changing {{FULLPAGENAMEE}} to {{#ifeq:{{NAMESPACENUMBER}}|-1|{{#titleparts:{{FULLPAGENAMEE}}|0|2}}|{{FULLPAGENAMEE}}}} should fix it. — JJMC89 (T·C) 11:47, 12 March 2016 (UTC)

Switching {{FULLPAGENAME}} to {{#switch:{{ROOTPAGENAME}}|MovePage={{SUBPAGENAME}}|{{FULLPAGENAME}}}} may work as well. Jo-Jo Eumerus (talk, contributions) 11:55, 12 March 2016 (UTC)

That would only work for pages that are not subpages since {{SUBPAGENAME}} is bar for all of Special:MovePage/Foo/bar, Special:MovePage/Talk:Foo/baz/bar, etc. — JJMC89 (T·C) 12:10, 12 March 2016 (UTC)

It would apparently fail in the opposite direction. It seems the special namespace does not have subpages. {{SUBPAGENAME:Special:MovePage/Talk:Foo/baz/bar}} produces MovePage/Talk:Foo/baz/bar. But #titleparts does work on special pages so your own code looks correct. PrimeHunter (talk) 14:10, 12 March 2016 (UTC)

Totally didn't test it, my bad. Thanks for catching that. The Special namespace is special. — JJMC89 (T·C) 21:20, 12 March 2016 (UTC)

I have tested and added the above code by JJMC89.[1] PrimeHunter (talk) 14:16, 16 March 2016 (UTC)

@JJMC89 @Jo-Jo Eumerus @PrimeHunter: The fix resulted in a new problem for page titles with spaces (e.g. 2000 Sri Lanka cyclone, A Weekend in the City, Template:Edit fully-protected, etc.). The problem is caused by the titleparts parser function because the output always contains spaces instead of underscores regardless of {{FULLPAGENAMEE}} or {{FULLPAGENAME}} being used. I propose using {{urlencode}} as shown below. And since {{urlencode}} will be used I also propose replacing {{FULLPAGENAMEE}} with {{FULLPAGENAME}}. The following line should replace line 24 in the template code: <li>{{{log-text|The reason for protection can be found in the [{{fullurl:Special:Log|type=protect&page={{urlencode:{{#ifeq:{{NAMESPACENUMBER}}|-1|{{#titleparts:{{FULLPAGENAME}}|0|2}}|{{FULLPAGENAME}}}}}}}} protection log]. If there are no relevant entries in the protection log, the page may have been moved after being protected.}}} -- SLV100 (talk) 21:34, 23 March 2016 (UTC)

The requested change is in the sandbox. — JJMC89 (T·C) 22:10, 23 March 2016 (UTC)

It works for all context titles I tested at Special:ExpandTemplates so I have added it to the live template.[2] PrimeHunter (talk) 22:27, 23 March 2016 (UTC)

Protected edit request on 26 April 2016

Moved from Template talk:Protected page text/extendedconfirmed

 – {{3x|p}}ery (talk) 01:10, 19 February 2019 (UTC)

The section link to "extended confirmed users" doesn't work since the section name was changed. Should be changed from [[Wikipedia:User access levels#Extended confirmed|extended confirmed users]] to [[Wikipedia:User_access_levels#Extended_confirmed_users|extended confirmed users]]. Techman224^Talk 04:32, 26 April 2016 (UTC)

Done — Martin (MSGJ · talk) 08:26, 26 April 2016 (UTC)

Protected edit request on 14 May 2016

For the "Request unprotection" link, consider changing the nonexistent section link [[Wikipedia:Requests for page protection#Current requests for unprotection]] to the page itself, or the renamed section: [[Wikipedia:Requests for page protection#Current requests for reduction in protection level]] — Andy W. (talk · ctb) 04:07, 14 May 2016 (UTC)

Done I used the new section heading, and tweaked the wording to match as well. Thanks for pointing this out! — Mr. Stradivarius ^{♪ talk ♪} 07:45, 14 May 2016 (UTC)

Protected edit request on 15 October 2016

Moved from Template talk:Protected page text/extendedconfirmed

 – {{3x|p}}ery (talk) 01:10, 19 February 2019 (UTC)

WP:ECP2016 concluded in August that 30/500 protection may be used by administrators to combat any form of disruption, not just in topics authorized by the Arbitration Committee. Accordingly, we should amend the text under |protection-reason= to read something along the lines of: While most articles can be edited by anyone, extended confirmed protection is sometimes necessary to prevent disruptive editing on controversial pages. I have sandboxed my proposed changes at Template:Protected page text/extendedconfirmed/sandbox (see diff). I've also added a link to Wikipedia:Disruptive editing – feel free to leave that out if you feel it's unnecessary.

Mz7 (talk) 22:18, 15 October 2016 (UTC)

Done — Martin (MSGJ · talk) 18:32, 16 October 2016 (UTC)

Icon for cascade protection

There is a request at MediaWiki talk:Cascadeprotected#Request for update that the icon used for cascade protection should be turquoise. Is this a good idea and if so, can it be implemented here? — Martin (MSGJ · talk) 06:30, 16 October 2017 (UTC)

Pinging template maintainer Mr. Stradivarius — Martin (MSGJ · talk) 10:32, 20 October 2017 (UTC)

@MSGJ: Now done. This template has an image parameter, so I just used that on MediaWiki:Cascadeprotected. — Mr. Stradivarius ^{♪ talk ♪} 00:32, 21 October 2017 (UTC)

Thank you — Martin (MSGJ · talk) 07:27, 23 October 2017 (UTC)

Protected edit request on 27 November 2017

Moved from Template talk:Protected page text/extendedconfirmed

 – {{3x|p}}ery (talk) 01:10, 19 February 2019 (UTC)

Change:

| protection-message = This page is currently [[Wikipedia:Protection policy#Arbitration 30/500 protection|protected]] so that only [[Wikipedia:User access levels#Extended confirmed users|extended confirmed users]] and [[Wikipedia:Administrators|administrators]] can {{{2}}} it.

to

| protection-message = This page is currently [[Wikipedia:Protection policy#Arbitration 30/500 protection|protected]] so that only [[Wikipedia:User access levels#Extended confirmed users|extended confirmed users]] can {{{2}}} it.

and change

| who-can-edit = An [[Wikipedia:Administrators|administrator]] or [[Wikipedia:User access levels#Extended confirmed users|extended confirmed user]]

to

| who-can-edit = An [[Wikipedia:User access levels#Extended confirmed users|extended confirmed user]]

Saying "extended confirmed" and "administrators" is redundant since all admins are automatically extended confirmed users. Ahecht (TALK
PAGE) 20:11, 27 November 2017 (UTC)

No, it is not redundant. Admins are explicitly excluded from being automatically granted the extendedconfirmed user group unless manually added. — JJMC89 (T·C) 03:18, 28 November 2017 (UTC)

Proposed text change

I am proposing changing the phrase If you have noticed an error or have a suggestion for a simple change... to If you have noticed an error or have a suggestion for a simple, non-controversial change.... Controversial changes, no matter how simple, should be discussed before an edit request is opened. --Ahecht (TALK
PAGE) 20:53, 20 December 2017 (UTC)

After a few months of no objection, I'm opening an edit request. --Ahecht (TALK
PAGE) 21:24, 12 March 2018 (UTC)

 Note: support change but cannot find that text on the specified subtemplate — Martin (MSGJ · talk) 21:41, 12 March 2018 (UTC)

@MSGJ: The phrase was in the parent template. I have corrected the request. --Ahecht (TALK
PAGE) 21:58, 12 March 2018 (UTC)

 Done — Martin (MSGJ · talk) 22:03, 12 March 2018 (UTC)

Suggestion

{{Protected page text}} and its subpages, /semi, /extendedconfirmed, /template, and /full, are meant to be transcluded at MediaWiki:Protectedpagetext (which by default is fully protected). It would be possible to enable cascading-protection on these pages rather than having to actually fully protect them. 2600:1700:A2A0:FB50:1DF7:5A79:920F:AEF8 (talk) 02:08, 14 August 2018 (UTC)

Protected edit request on 13 November 2018

 Administrator note  On hold Pending local upload and protection of files. — xaosflux ^Talk 04:03, 13 November 2018 (UTC)

Local upload and protection is now complete. ∰Bellezzasolo✡ Discuss 12:26, 13 November 2018 (UTC)

 Done Got 'em. Even added your Interface one. There are a few other places but I think grabbed the big ones. Will check later for others. ~ Amory (u • t • c) 23:17, 14 November 2018 (UTC)

Template:Protected page text

Change the line:
| image = [[File:{{{image|Padlock.svg}}}|40x40px|link=|alt=]]
to:
| image = [[File:{{{image|Full-protection-shackle.svg}}}|40x40px|link=|alt=]]

Template:Protected page text/extendedconfirmed

Change the line:
| image = Padlock-blue.svg
to:
| image = Extended-protection-shackle.svg

Template:Protected page text/full

Change the line:
| image = Padlock{{#switch:{{{2}}}|move=-olive|upload=-purple|create=-skyblue}}.svg
to:
| image = {{#ifeq:{{{2|}}}|edit|Full|{{{2|Full}}}}}-protection-shackle.svg

Template:Protected page text/semi

Change the line:
| image = Padlock-silver.svg
to:
| image = Semi-protection-shackle.svg

Template:Protected page text/template

Change the line:
| image = Padlock-pink.svg
to:
| image = Template-protection-shackle.svg

Per this RfC ∰Bellezzasolo✡ Discuss 02:40, 13 November 2018 (UTC)

• • Oppose all. It isn't broken. The old padlocks actually look like padlocks, unlike these fugly icons, which look like shopping bags. Kamafa Delgato _(Lojbanist)^{Styrofoam is not made from kittens.} 03:44, 13 November 2018 (UTC)
    • @Lojbanist: that battle is already lost, the RfC passed 23 to 3. This is just implementing consensus. ∰Bellezzasolo✡ Discuss 04:02, 13 November 2018 (UTC)

attempted-action

There appears to be an |attempted-action= parameter which isn't documented (I see it in use at MediaWiki:Cascadeprotected).  — SMcCandlish ☏ ¢ 😼  00:08, 7 December 2018 (UTC)

No such parameter is or has been used by the template. Jackmcbarn requested it in template calls at #Protected edit request on 29 August 2014 and MediaWiki talk:Cascadeprotected#Protected edit request on 28 August 2014. As far as I can tell, he made no request for code to actually use it. He has not edited since 2017. translatewiki:MediaWiki:Cascadeprotected/qqq says the corresponding MediaWiki parameter $3 is unused. PrimeHunter (talk) 00:47, 7 December 2018 (UTC)

Protected edit request on 19 February 2019

Replace "established registered users" with "autoconfirmed users", with a link to Wikipedia:User access levels#Autoconfirmed, as "autoconfirmed" is the proper term for that user group. {{3x|p}}ery (talk) 00:26, 19 February 2019 (UTC)

 Partly done - linked to Wikipedia:User_access_levels#Autoconfirmed, but left other link. Part of the point of the existing link is to encourage users to sign up for accounts. — xaosflux ^Talk 18:04, 23 February 2019 (UTC)

Protected edit request on 19 February 2019 (2)

Create MediaWiki:Customjsprotected and MediaWiki:Customcssprotected with the content {{protected page text/interface|type=js|$1|$2}} and {{protected page text/interface|type=css|$1|$2}} respectively. The purpose of this edit request is to harmonize the error messages shown when trying to edit someone else's JS or CSS page with that when shown in all other "you can't edit this" error messages. {{3x|p}}ery (talk) 01:27, 19 February 2019 (UTC)

 Done — xaosflux ^Talk 18:07, 23 February 2019 (UTC)

Looks like a few things went wrong here.  Investigating.... {{3x|p}}ery (talk) 18:21, 23 February 2019 (UTC)

@Xaosflux: When I went to see the source for someone else's script, I was told:

This User script is protected so that only RhinosF1 and Interface administrators can $2 it.

Could we remove the capital from User script, and fix the $2 to report the attempted action (edit)? Thanks, --DannyS712 (talk) 18:36, 23 February 2019 (UTC)

@DannyS712: I'm currently in the process of coding up a change to fix that. {{3x|p}}ery (talk) 18:46, 23 February 2019 (UTC)

@Pppery: Thanks --DannyS712 (talk) 18:47, 23 February 2019 (UTC)

@Xaosflux: Looks like we both made some mistakes in this edit request, and therefore I have to make a followup "cleanup" one.

1. You swapped the content of the two MediaWiki pages I requested: type=js belongs on MediaWiki:Customjsprotected and type=css belongs on MediaWiki:Customjsprotected, not the other way around.
2. MediaWiki:Customjsprotected and MediaWiki:Customcssprotected don't take parameters in the way I expected, they should both be {{protected page text/interface||$1..., not {{protected page text/interface|$1|$2....
3. I made a few coding and formatting errors in Template:Protected page text/interface, and therefore the sandbox of that template needs to be synced to fix them.

. It's unfortunately difficult to test changes involving system messages. {{3x|p}}ery (talk) 18:54, 23 February 2019 (UTC)

@DannyS712: Alerting you to this too. {{3x|p}}ery (talk) 18:58, 23 February 2019 (UTC)

@Pppery: I just went to try and test it on the beta cluster, but its currently on read-only. I'll try again later --DannyS712 (talk) 19:15, 23 February 2019 (UTC)

• I've reverted these messages to default. Ping me and reactivate the edit request when there is a good version ready to put in. — xaosflux ^Talk 20:40, 23 February 2019 (UTC)

Ok, xaosflux and DannyS712, I believe I've coded a fixed version. I also decided to go the extra mile and do it for user JSON pages.

1. Move User:Pppery/MediaWiki:customcssprotected, User:Pppery/MediaWiki:customjsprotected, and User:Pppery/MediaWiki:customjsonprotected into MediaWiki namespace (dropping the "User:Pppery" from the title) without leaving a redirect
2. Sync the sandbox of Template:Protected page text/interface.
3. Protect Template:Protected page text/user-json.

It would also be good for someone more knowledgable as to why user JSON pages are protected to copy-edit some of the wording on that template, but that doesn't block this from going live.
Thanks for fulfilling all of my (admittedly highly technical in nature) edit requests to MediaWiki namespace. {{3x|p}}ery (talk) 00:00, 24 February 2019 (UTC)

@Pppery: I expanded the user-json to try and explain why --DannyS712 (talk) 00:19, 24 February 2019 (UTC)

Side note: I discovered phab:T216899 and phab:T216900, two bugs related to moving a page, during the process of testing this change. {{3x|p}}ery (talk) 04:00, 24 February 2019 (UTC)

•  Done — xaosflux ^Talk 13:58, 9 March 2019 (UTC)

@Xaosflux: MediaWiki:Customcssprotected and MediaWiki:Customjsprotected are currently calling the sandbox of Template:Protected page text/interface (Yes, I am aware that this is my fault). {{3x|p}}ery (talk) 16:49, 9 March 2019 (UTC)

@Pppery: do you have specific fixes (or I can just revert to the last setting while it is figured out)? — xaosflux ^Talk 16:55, 9 March 2019 (UTC)

@Xaosflux: Remove /sandbox from both MediaWiki:Customcssprotected and MediaWiki:Customjsprotected. {{3x|p}}ery (talk) 16:56, 9 March 2019 (UTC)

@Pppery: oh! (I misread what you wanted done). This is fixed now. — xaosflux ^Talk 16:57, 9 March 2019 (UTC)

At least this protection-level slip-up lasted for only 1/21900 as long as the previous one I requested be fixed. {{3x|p}}ery (talk) 17:00, 9 March 2019 (UTC)

Protected edit request on 24 February 2019

Copy all code from User:Pppery/MediaWiki:Cascadeprotected and User:Pppery/MediaWiki:Protectedpagetext to the corresponding MediaWiki pages. This:

1. Fixes the notice for cascade-protected pages that transclude themselves, such as Wikipedia:Cascade-protected items/content. (yes, I am aware I could fix this by creating Template:Editnotices/Protection/Wikipedia:Cascade-protected items/content, but it seems wiser to me to fix the bug at its source rather than work around it)
2. Moves the content of MediaWiki:Cascadeprotected to Template:Protected page text/cascade for consistency reasons.
3. Implements the fix for moves for cascade protection, where it seems to have been forgotten. @DannyS712: Feel like copyediting Template:Protected page text/cascade like you did for my previous reqeust?

I've done some testing of this using Special:ExpandTemplates and a module I wrote to simulate system messages, but of course it's not possible to text 100% of the code involved in a system message change when you aren't an admin on any Wikimedia wiki.

Sorry for having to make so many edit requests to system messages. {{3x|p}}ery (talk) 03:33, 24 February 2019 (UTC)

Pinging Mr. Stradivarius, who introduced the somewhat obscure bug that I'm fixing in point 1 and is the true motivation for this request. {{3x|p}}ery (talk) 03:37, 24 February 2019 (UTC)

I'm assuming that the bug you found is that the message in this template should display on cascade-protected pages that transclude themselves, but it currently isn't. Do I have that right? Also, how about requesting adminship on the test wiki? If you ever need to test stuff that's developer-related then you should be able to get it without much fuss. Best — Mr. Stradivarius ^{♪ talk ♪} 15:30, 24 February 2019 (UTC)

@Mr. Stradivarius: You're right, or to be more precise self-transclusions should be entirely ignored when deciding which protection message to display. {{3x|p}}ery (talk) 17:01, 24 February 2019 (UTC)

@Pppery: I’m getting home in ~1 hour. I can proofread it and, if the database is no longer read only, text is out on the beta cluster (where I’m an admin). —DannyS712 (talk) 03:41, 24 February 2019 (UTC)

@Pppery: I think I've copied them all over if you want to take a look at the beta cluster --DannyS712 (talk) 07:07, 26 February 2019 (UTC)

A test at a page on the beta cluster that transcludes itself shows that the correct error message does display. So, Xaosflux, I think this is ready to sync. {{3x|p}}ery (talk) 20:41, 26 February 2019 (UTC)

 Done should this cause any errors, any admin should revert ASAP. — xaosflux ^Talk 02:27, 13 March 2019 (UTC)

Seems to work! {{3x|p}}ery (talk) 02:43, 13 March 2019 (UTC)

Protected edit request on 24 February 2019 (2)

Another day (in my timezone, at least), another obscure protection-message bug to edit-request fix, this time involving site JS, CSS and JSON:

1. Move User:Pppery/MediaWiki:Protectedinterface, User:Pppery/MediaWiki:Sitecssprotected, and User:Pppery/MediaWiki:Sitejsprotected into MediaWiki namespace.
2. Create MediaWIki:Sitejsonprotected with no content. (all users who can edit the MediaWiki namespace can also edit site JSON)
3. (Template:Protected interface will need to be documented and protected)

This edit request:

1. Removes the duplicate You do not have permission to edit this CSS page because it may affect all visitors. message shown when trying to edit site CSS/JS/JSON as a non-admin
2. Fixes the error message shown when an admin who isn't an interface admin tries to edit site CSS/JS.
3. Implements the fix for moves for protection of pages in the MediaWiki namspace (where it was missed)
4. Fixes the content model detection to work when moving a page.

@Xaosflux and DannyS712: {{3x|p}}ery (talk) 19:27, 24 February 2019 (UTC)

@Pppery: I don't see any issues --DannyS712 (talk) 19:37, 24 February 2019 (UTC)

@Pppery: MediaWIki:Sitejsonprotected appears to be legitimately used when encountering pages such as: MediaWiki:Sandbox/test.json. — xaosflux ^Talk 19:52, 24 February 2019 (UTC)

@Xaosflux: But Mediawiki:Protectedinterface will also occur in the same place. Don't you agree than that message is redundant to the big box immediately above it? {{3x|p}}ery (talk) 19:53, 24 February 2019 (UTC)

@DannyS712: the beta cluster is no longer read-only. {{3x|p}}ery (talk) 04:45, 26 February 2019 (UTC)

@Pppery: I don't think I'm going to have time before tonight (utc) --DannyS712 (talk) 04:47, 26 February 2019 (UTC)

Not a problem, after all this request has sat idle for three days anyway. {{3x|p}}ery (talk) 04:49, 26 February 2019 (UTC)

@DannyS712: You forgot to import Module:Page, which is causing a duplicate protection error message to show up. {{3x|p}}ery (talk) 20:26, 26 February 2019 (UTC)

@Pppery: I don't know where the error is, but I copied module:page over (and module:CallAssert, which page calls) --DannyS712 (talk) 20:31, 26 February 2019 (UTC)

@DannyS712: You missed Module:Protect, which is called by Module:Page. {{3x|p}}ery (talk) 20:33, 26 February 2019 (UTC)

@Pppery:  Done --DannyS712 (talk) 20:35, 26 February 2019 (UTC)

@DannyS712: Sorry for going through so many testing iterations here, but it looks like you copied the wrong content: MediaWiki:Protectedinterface should have the content of User:Pppery/MediaWiki:Protectedinterface, but you created it with content from User:Pppery/MediaWiki:Sitecssprotected or User:Pppery/MediaWiki:Sitejsprotected (you also forgot to create MediaWiki:Sitejsonprotected with no content, but that's easy to fix. {{3x|p}}ery (talk) 20:44, 26 February 2019 (UTC)

@Pppery:  Done x2 --DannyS712 (talk) 20:48, 26 February 2019 (UTC)

Seems to work aside from a few more copying errors. {{3x|p}}ery (talk) 20:51, 26 February 2019 (UTC)

 Done — xaosflux ^Talk 20:06, 23 March 2019 (UTC)

@Xaosflux: You created MediaWiki:MediaWiki:Sitejsprotected with a double namespace prefix. {{3x|p}}ery (talk) 20:37, 23 March 2019 (UTC)

@Pppery:  Fixed — xaosflux ^Talk 20:39, 23 March 2019 (UTC)

Protected edit request on 20 March 2019

In {{Protected page text/user-json}}, please replace

| protection-message = This user JSON page is currently [[Wikipedia:Protection policy#Permanent protection|protected]] so that only {{#switch:{{{2}}}|move={{PAGENAME:{{#titleparts:{{PAGENAME}}|1|2}}}}|#default={{ROOTPAGENAME}}}} and [[Wikipedia:Administrators|administrators]] can {{{2}}} it.

with

| protection-message = This user JSON page is currently [[Wikipedia:Protection policy#Permanent protection|protected]] so that only {{#switch:{{{2}}}|move={{PAGENAME:{{#titleparts:{{PAGENAME}}|1|2}}}}|#default={{ROOTPAGENAME}}}}, [[Wikipedia:Administrators|administrators]], and [[Wikipedia:Interface administrators|Interface administrators]] can {{{2}}} it.

This is because interface administrators can also edit user JSON pages (search for edituserjson in Special:ListGroupRights)

Thanks, --DannyS712 (talk) 23:44, 20 March 2019 (UTC)

 Not done. Per Wikipedia_talk:Interface_administrators/Archive_3#Allow_non-admins_to_request_access?, non-admins will not be allowed to request access to interface administrator at the this time., so this change is pointless wording bloat. {{3x|p}}ery (talk) 00:04, 21 March 2019 (UTC)

MediaWiki:Customjsonprotected

(Pinging @Xaosflux and Pppery: as the people who wrote this message) Is there a reason why MediaWiki:Customjsonprotected uses this template rather than its own custom text like MediaWiki:Customcssjsprotected? Especially as the JSON protection is not a protection that is applied by admins; thus parts of the text on MediaWiki:Customjsonprotected are wrong. Jo-Jo Eumerus (talk, contributions) 08:58, 7 June 2019 (UTC)

@Jo-Jo Eumerus: MediaWiki:Customcssjsprotected is a message that is no longer used by the software, so it provides nothing to compare to (the actual messages that appear when a non-iadmin attempts to edit someone else's user CSS/JS are MediaWiki:Customcssprotected and MediaWiki:Customjsprotected, both of which call Template:Protected page text/interface). As to why I chose to use Template:Protected page text, custom text like that appears to me to provide less information, including the lack of an edit request button, for no apparent benefit If you think something needs changing in the wording of Template:Protected page text/interface and Template:Protected page text/user-json, then feel free to change it. * Pppery * _{it has begun...} 11:31, 7 June 2019 (UTC)

Protected edit request on 31 July 2019

I need the above footer header to be: This page is currently [[Wikipedia:Protection policy#Semi-protection|protected]] so that only [[Wikipedia:User_access_levels#Autoconfirmed|established]], [[Wikipedia:Why create an account?|registered users]] and [[Wikipedia:Administrators|administrators]] can {{{2}}} it. because all the other messages say that, too. Mr. Juicyfun (talk) 23:47, 31 July 2019 (UTC)

 Not done administrators are also autoconfirmed users, so it doesn't need to be called out. — xaosflux ^Talk 02:09, 1 August 2019 (UTC)

Protected edit request on 1 August 2019

In the suggestions parameter, change the value "yes" to {{#ifexist:{{FULLPAGENAME}}|yes}}. Mr. Juicyfun ^{(Obliterator time!)} 04:10, 1 August 2019 (UTC)

Hrm. Is it agreed upon that the "What can I do?" text should not display on non-existent pages? (The effect of the edit request would be to hide that text when someone tried to edit a salted page) Jo-Jo Eumerus (talk, contributions) 08:23, 1 August 2019 (UTC)

Um, I think so. Mr. Juicyfun ^{(Obliterator time!)} 17:07, 1 August 2019 (UTC)

 Not done why would we make it harder for someone to make an ER on a salted page? This would need more discussion at least. — xaosflux ^Talk 18:32, 1 August 2019 (UTC)

Protected edit request on 27 August 2019

I think talking about move protection when the user is trying to edit the page is not useful, and it makes this message longer while it should be as concise as possible. Therefore, please replace:

<li> For move-protected pages, see [[Wikipedia:requested moves|requested moves]].
</li>

With:

{{#ifeq: {{{attempted-action}}} | move |
<li> For move-protected pages, see [[Wikipedia:requested moves|requested moves]].
</li>
}}

This way, the item should display when attempting to move a page (e.g. [3]), but not when attempting to edit it (e.g. [4]). Matma Rex talk 11:40, 28 August 2019 (UTC)

@Matma Rex: For intended use on which page(s)? --Izno (talk) 16:54, 2 September 2019 (UTC)

@Izno: I'm not sure what you mean – the template is used in interface messages when a page is protected (check out the two links I gave above while logged out). Matma Rex talk 17:21, 2 September 2019 (UTC)

I saw that after--I think the specific interface pages for this parameter would be good to document. --Izno (talk) 17:35, 2 September 2019 (UTC)

The parameter is already in use, on every interface message using this template that I checked. Sorry, I can’t easily make a list now. Matma Rex talk 13:02, 3 September 2019 (UTC)

I... don't see that? The parameter you're suggesting to add is entirely new so far as I can tell. Am I reading you wrong? --Izno (talk) 01:59, 4 September 2019 (UTC)

It's called indirectly via subtemplates [5] which can get the value from MediaWiki:Permissionserrorstext-withaction. But I oppose the suggestion. The move link disappears when you cannot move the page so users may try "View source" instead to get info. PrimeHunter (talk) 09:57, 4 September 2019 (UTC)

 Not done as to the immediate edit request, discussion can certainly continue below - once a consensus emerges, feel free to reactivate the request. — xaosflux ^Talk 13:44, 8 September 2019 (UTC)

Protected edit request on 21 March 2020

In the line for new editors, please replace

[[Wikipedia:New contributors' help page|Find out more about how to get started editing Wikipedia]].

(and old page which now redirects to WP:Questions) with

[[Help:Introduction|Find out more about how to get started editing Wikipedia]].

This will send them to a more appropriate introductory page. Sdkb (talk) 07:02, 21 March 2020 (UTC)

 Done Izno (talk) 15:00, 21 March 2020 (UTC)

Protected edit request on 22 May 2020

Please change This page is currently [[Wikipedia:Protection policy#Template protection|protected]] so that only [[Wikipedia:Template editors|template editors]] and [[Wikipedia:Administrators|administrators]] can {{{2}}} it. to This page is currently [[Wikipedia:Protection policy#Template protection|protected]] so that only [[Wikipedia:Template editors|template editors]] and [[Wikipedia:Administrators|administrators]] can {{{2}}} {{#ifeq:{{{2}}}|create|it|the templates}}. Thank you. The secret weapon for the account Denimbabel 23:17, 22 May 2020 (UTC)

@Denimalt: What is the point of this change? * Pppery * _{it has begun...} 18:44, 23 May 2020 (UTC)

Just template editors can edit the templates and change their name. The secret weapon for the account Denimbabel 19:07, 23 May 2020 (UTC)

I also do not understand the purpose of this — Martin (MSGJ · talk) 21:55, 23 May 2020 (UTC)

Disabled for now — Martin (MSGJ · talk) 21:22, 24 May 2020 (UTC)

Protected edit request on 7 August 2020

Please make these changes. Jackmcbarn (talk) 05:15, 7 August 2020 (UTC)

@Jackmcbarn: why would we need to invoke the {{u}} template here as opposed to say just using a wikilink? — xaosflux ^Talk 16:50, 7 August 2020 (UTC)

@Xaosflux: The pipe trick expands in the source code during the pre-save transform instead of during rendering, so we can't just do [[User:{{#switch:{{{2}}}|move={{PAGENAME:{{#titleparts:{{PAGENAME}}|1|2}}}}|#default={{ROOTPAGENAME}}}}|]]. That gives us 3 choices:

1. Use {{u}} like I did in the sandbox
2. Don't use a pipe at all, and accept that the message will say "only User:Example and interface administrators" instead of "only Example and interface administrators"
3. Duplicate the username detection logic manually on the other side of the pipe, which results in this kind of redundant messiness: [[User:{{#switch:{{{2}}}|move={{PAGENAME:{{#titleparts:{{PAGENAME}}|1|2}}}}|#default={{ROOTPAGENAME}}}}|{{#switch:{{{2}}}|move={{PAGENAME:{{#titleparts:{{PAGENAME}}|1|2}}}}|#default={{ROOTPAGENAME}}}}]]

If you don't like option 1, my next preference would be for option 2 instead. By the way, why don't you want to use {{u}} here? Jackmcbarn (talk) 21:03, 7 August 2020 (UTC)

@Jackmcbarn: because then we should raise protection on it from TP to FP, as it will be part of the interface - and I'd rather avoid extra protections if not necessary. — xaosflux ^Talk 00:01, 8 August 2020 (UTC)

@Xaosflux: Is there a requirement somewhere that every template used in an interface message needs to be fully protected rather than just template-protected? I don't see that at WP:FULL. But in any case, are you okay with option 2 instead then? Jackmcbarn (talk) 00:04, 8 August 2020 (UTC)

@Jackmcbarn: as MediaWiki is FP, transclusions get it to avoid weaking the namespace protection. So right now this outputs something along the lines of This user script is protected so that only Jackmcbarn and interface administrators can edit it., and it says it when you are already on a subpage, with subpage navigation to the userpage - are you finding it confusing with out the text "User:" also being displayed? — xaosflux ^Talk 00:09, 8 August 2020 (UTC)

@Xaosflux: My preference was actually to not display the "User:" prefix, hence why I went with option 1 and not 2 from the beginning. I just want the user's name to be a wikilink. But I'm fine with option 2 if it avoids fully protecting another template. Jackmcbarn (talk) 00:11, 8 August 2020 (UTC)

Template:User is already used in the MediaWiki namespace, so this argument does not apply. * Pppery * _{it has begun...} 00:45, 8 August 2020 (UTC)

@Pppery: thanks for the note, it is not automatic, I've upped that one. — xaosflux ^Talk 00:59, 8 August 2020 (UTC)

Actually, reverted that, just got rid of its needless use on that message. — xaosflux ^Talk 01:01, 8 August 2020 (UTC)

So for your option 2, what do you want to change this to:

{{#switch:{{{2}}}|move={{PAGENAME:{{#titleparts:{{PAGENAME}}|1|2}}}}|#default={{ROOTPAGENAME}}}}

— xaosflux ^Talk 10:45, 8 August 2020 (UTC)

@Xaosflux: This. Jackmcbarn (talk) 16:36, 8 August 2020 (UTC)

 Done — xaosflux ^Talk 16:40, 8 August 2020 (UTC)

Protected edit request on 26 August 2020

In If you have noticed an error or have a suggestion for a simple, non-controversial change …, please remove the excess space before change within the source code.--Hildeoc (talk) 08:29, 26 August 2020 (UTC) Hildeoc (talk) 08:29, 26 August 2020 (UTC)

 Done — xaosflux ^Talk 03:11, 28 August 2020 (UTC)

Protected edit request on 5 November 2020

Please change therefore only administrators can edit it to so only administrators can edit to to fix the comma splice. Thanks! {{u|Sdkb}} ^talk 02:42, 5 November 2020 (UTC)

 Done — xaosflux ^Talk 16:41, 5 November 2020 (UTC)

Discussion at Wikipedia:Village pump (idea lab) § The edit requests time sink

 You are invited to join the discussion at Wikipedia:Village pump (idea lab) § The edit requests time sink. {{u|Sdkb}} ^talk 07:11, 3 December 2020 (UTC)

Protected edit request on 8 February 2021

Please add in {{Protected page text/extendedconfirmed}} the following:

If you have a user account, log in first. If you do not yet have an account, you may create one; after 30 days and 500 edits, you will be able to edit pages with extended confirmed protection.

Thanks. Rodney Araujo Tell me - My contributions 16:53, 8 February 2021 (UTC)

Rodney Araujo, there's already a link to WP:Extended confirmed; what are you hoping to improve by adding the above language? {{u|Sdkb}} ^talk 19:23, 8 February 2021 (UTC)

@Sdkb: I need that please include this to help to non extended confirmed users to how will can get the extended confirmed right. Rodney Araujo Tell me - My contributions 21:05, 8 February 2021 (UTC)

 Not done @Rodney Araujo: please mock up your change in the sandbox, test it, then reactivate the edit request when ready. @Sdkb: this sounds useful and would give the same sort of response for SPP as ECP for logged out users. — xaosflux ^Talk 14:48, 9 February 2021 (UTC)

Protected edit request on 15 June 2021

Replace [[Wikipedia:Template editors|template editors]] with [[Wikipedia:template editor|]]s in {{Protected page text/template}} for cleanliness in the wikitext, and to not link to a redirect. Before: template editors. After: template editors. SWinxy (talk) 18:38, 15 June 2021 (UTC)

Looks like a good fix, as full-protected interface pages shouldn't use redirects. {{u|Sdkb}} ^talk 18:44, 15 June 2021 (UTC)

 Partly done in any event, the redirect has been bypassed (I skipped link magix). — xaosflux ^Talk 18:47, 15 June 2021 (UTC)

Cool. Thanks! SWinxy (talk) 19:36, 15 June 2021 (UTC)

Proposed tweaks to multi-column layout

This message is always shown in two columns on desktop devices (minimum 720px screen width), but sometimes it can be displayed in a fairly narrow space even on wide screens (for example: visit visual editor on a protected page or new topic tool on a protected page while logged out).

I'd like to propose some tweaks, so that it will be shown in a single column in those cases: User:Matma Rex/Template:Protected page text/styles.css (diff).

Matma Rex talk 18:25, 20 July 2022 (UTC)

 Done @Matma Rex: this has been loaded, my initial tests seem fine across several skins. If anyone sees anything causing major breakages please revert and note the issue here for follow up. — xaosflux ^Talk 14:43, 22 July 2022 (UTC)

@Xaosflux It looks like you lost the last part of the code when copying, starting from .pptext-whywhat > div. This effectively removes the multi-column layout. I'd be okay with that, but I don't think it was intentional? Matma Rex talk 14:53, 22 July 2022 (UTC)

@Matma Rex resynced, not sure where that went, thanks for the note. — xaosflux ^Talk 15:20, 22 July 2022 (UTC)