Template talk:Protected page text
![]() | To help centralise discussions and keep related topics together, several talk subpages of Template:Protected page text redirect here. These include the talk pages of Template:Protected page text/semi, Template:Protected page text/extendedconfirmed, Template:Protected page text/template, Template:Protected page text/user-json, Template:Protected page text/full, Template:Protected page text/cascade and Template:Protected page text/interface plus their documentation pages, sandboxes and test cases pages. |
![]() Archives (Index) |
This page is archived by ClueBot III.
|
Proposed tweaks to multi-column layout
editThis edit request to Template:Protected page text/styles.css has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
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)
- @Xaosflux It looks like you lost the last part of the code when copying, starting from
Protected edit request on 12 October 2022
editThis edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Please implement my changes in the sandbox. The reason for this is that the message MediaWiki:Titleprotected does not show up if the page does not exist anymore (see phab:T312317). This workaround will make sure that an editor visiting a protected page will always know why they cannot create the page. Same information from titleprotected but more, just phrased differently.
I also mention "please save the text temporarily to your device" from the title blacklist forbidden page as pages might be protected suddenly while an editor is working on it. I believe these changes to be non-controversial because it largely replaces functionality for MediaWiki:Titleprotected as that message is not working as it is supposed to. Aasim - Herrscher of Wikis ❄️ 17:39, 12 October 2022 (UTC)
- Done though this seems to be getting overly complicated. — xaosflux Talk 14:34, 29 December 2022 (UTC)
Fully-protected edit request on 9 November 2023
editThis edit request to Template:Protected page text/interface has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
I would suggest removing the user page link and prefix to show as "This user CSS page/user script is currently protected so that only Protected page text and interface administrators can {{{2}}} it" to maintain consistency with Template:Protected page text/user-json, or remove the unnecessary User: prefix while keeping the userpage link. And please see my request in wikitext so that you do not add Protected page text instead of the user's CSS/JS page. Thanks. 64andtim (talk to me) 15:37, 9 November 2023 (UTC) 64andtim (talk to me) 15:37, 9 November 2023 (UTC)
- Not done See Template talk:Protected page text/Archive 1#Protected edit request on 7 August 2020 - the current situation is deliberate. * Pppery * it has begun... 18:16, 10 November 2023 (UTC)
Protected edit request on 9 November 2023
editThis edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Please implement my changes in the sandbox. This adds a parameter to specify the message for where page protection should be dropped, as well as adds a "title" parameter so a title can be manually specified. Awesome Aasim 17:57, 9 November 2023 (UTC)
- What's the use case for either of these? * Pppery * it has begun... 18:16, 10 November 2023 (UTC)
- Please see my work in Template:Protected page text/blacklist/sandbox. Here, the parameter would be used to tell users that they can request the title be whitelisted or removed from the blacklist. Awesome Aasim 22:22, 10 November 2023 (UTC)
- Done I'm note sure whether I agree reworking the blacklist message in that way is a good idea, but this change by itself is harmless. * Pppery * it has begun... 23:42, 10 November 2023 (UTC)
- Please see my work in Template:Protected page text/blacklist/sandbox. Here, the parameter would be used to tell users that they can request the title be whitelisted or removed from the blacklist. Awesome Aasim 22:22, 10 November 2023 (UTC)
Protected edit request on 21 December 2023
editThis edit request to Template:Protected page text/cascade has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Change "Wikipedia:Transclucion" to "Help:Transclusion" in the piped wikilink. Why: Obviously the former is a redirect that is vandalised due to the resulting redirection to the latter title. Toadette (Happy holiday!) 19:16, 21 December 2023 (UTC)
- Not done I just protected the redirect itself. It's only used in one interface page, so that'd be easy to change, but it's in a ton of articles because of template transclusion. It's barely being vandalized; were it a typical page at RFPP, I'd decline, but I think it's justified here. (FWIW, Link to the move discussion) ~ Amory (u • t • c) 23:29, 21 December 2023 (UTC)