![]() | This page has an
administrative backlog that requires the attention of willing administrators. Please replace this notice with {{ no admin backlog}} when the backlog is cleared. |
Welcome—request protection of a page, file, or template here. | ||
---|---|---|
Before requesting, read the protection policy. Full protection is used to stop edit warring between multiple users or to prevent vandalism to high-risk templates; semi-protection and pending changes are usually used to prevent IP and new user vandalism (see the rough guide to semi-protection); and move protection is used to stop pagemove revert wars. Extended confirmed protection is used where semi-protection has proved insufficient (see the rough guide to extended confirmed protection) After a page has been protected, it is listed in the page history and logs with a short rationale, and the article is listed on Special:Protectedpages. In the case of full protection due to edit warring, admins should not revert to specific versions of the page, except to get rid of obvious vandalism.
Request protection of a page, or increasing the protection level
Request unprotection of a page, or reducing the protection level
Request a specific to a protected page
Please request an edit directly on the protected page's talk page before posting here |
2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 |
Place requests for new or upgrading pending changes, semi-protection, full protection, move protection, create protection, template editor protection, or upload protection at the BOTTOM of this section. Check the archive of fulfilled and denied requests or, failing that, the page history if you cannot find your request. Only recently answered requests are still listed here.
Reason: Persistent changes to the player's club before an official transfer is announced and while there is a template that cautions against doing so. Vasil3fonov ( talk) 08:07, 4 July 2024 (UTC)
Semi-protection: requesting six-month semi in response to persistent sockpuppetry by the banned Australian Railroad IP. ~ Pbritti ( talk) 13:21, 4 July 2024 (UTC)
Temporary semi-protection: Persistent disruptive editing – Persistent disruptive editing by anonymous editor, likely editing outside of their account. livelikemusic ( TALK!) 13:46, 4 July 2024 (UTC)
Temporary semi-protection: Persistent disruptive editing – Persistent disruptive editing by anonymous editors. livelikemusic ( TALK!) 13:48, 4 July 2024 (UTC)
Temporary extended confirmed protection: Persistent disruptive editing – Persistent hijacking of redirect with WP:PROMO content for a non-notable company. Drm310 🍁 ( talk) 14:23, 4 July 2024 (UTC)
Reason: Persistent addition of unsourced content by IP editor. Ckfasdf ( talk) 14:51, 4 July 2024 (UTC)
Reason: WP:PIA Isi96 ( talk) 15:21, 4 July 2024 (UTC)
Reason: High level of IP disruption; all IP edits since the beginning of May have been disruptive. This article has, for some time now, been a magnet for apparent nationalistic POV-pushing on account of MG's current ownership. Sable232 ( talk) 15:25, 4 July 2024 (UTC)
Reason: Persistent vandalism by IP addresses and new accounts (all likely by the same person). JeffSpaceman ( talk) 15:48, 4 July 2024 (UTC)
Temporary extended confirmed protection: Persistent disruptive editing – Disruptive editing by IP hopper continues... ภץאคгöร 15:59, 4 July 2024 (UTC)
Indefinite template protection: High-risk template – Sync with parent. Sohom ( talk) 16:47, 4 July 2024 (UTC)
Reason: High level of ip vandalism Theonewithreason ( talk) 17:17, 4 July 2024 (UTC)
Indefinite semi-protection: Persistent disruptive editing – Including, but not limited to, a persistent date-changing vandal. – LaundryPizza03 ( d c̄) 17:25, 4 July 2024 (UTC)
Indefinite semi-protection: Persistent vandalism – Including, but not limited to, a persistent date-changing vandal. – LaundryPizza03 ( d c̄) 17:27, 4 July 2024 (UTC)
Indefinite semi-protection: Persistent disruptive editing – Including, but not limited to, a persistent date-changing vandal. – LaundryPizza03 ( d c̄) 17:27, 4 July 2024 (UTC)
Indefinite full protection: user doesnt want any messages. There have been some automated messages through twinkle and such so I think indef full would stop this per the user request of no messages. 48 JCL 17:32, 4 July 2024 (UTC)
Reason: Ongoing IP vandalism LucasR muteacc ( talk) 17:35, 4 July 2024 (UTC)
Reason: Disruptive Editing Ado1024 ( talk) 18:57, 4 July 2024 (UTC)
Reason: High level of IP vandalism. Kataadj ( talk) 19:26, 4 July 2024 (UTC)
Temporary semi-protection: Persistent disruptive editing – WP:DE by editors from Wikipedia:Sockpuppet investigations/Balakashyap, WP:LOUTSOCK. The article already exists in the redirect's location. Jeraxmoira🐉 ( talk) 19:34, 4 July 2024 (UTC)
Before posting, first discuss with the protecting admin at their talk page. Post below only if you receive no reply.
Check the archives if you cannot find your request. Only recently answered requests are still listed here.
Reason: Been protected 6+ years, lower activity, should we give unprotection a shot? Razorback250 ( talk) 01:24, 4 July 2024 (UTC)
Ideally, requests should be made on the article talk page rather than here.
{{
Edit protected}}
, {{
Edit template-protected}}
, {{
Edit extended-protected}}
, or {{
Edit semi-protected}}
to the article's talk page if you would like to make a change rather than requesting it here. Doing so will automatically place the page in the appropriate category for the request to be reviewed.{{
Edit COI}}
template should be used.
A historical archive of previous protection requests can be found at Wikipedia:Requests for page protection/Archive.
![]() | This page has an
administrative backlog that requires the attention of willing administrators. Please replace this notice with {{ no admin backlog}} when the backlog is cleared. |
Welcome—request protection of a page, file, or template here. | ||
---|---|---|
Before requesting, read the protection policy. Full protection is used to stop edit warring between multiple users or to prevent vandalism to high-risk templates; semi-protection and pending changes are usually used to prevent IP and new user vandalism (see the rough guide to semi-protection); and move protection is used to stop pagemove revert wars. Extended confirmed protection is used where semi-protection has proved insufficient (see the rough guide to extended confirmed protection) After a page has been protected, it is listed in the page history and logs with a short rationale, and the article is listed on Special:Protectedpages. In the case of full protection due to edit warring, admins should not revert to specific versions of the page, except to get rid of obvious vandalism.
Request protection of a page, or increasing the protection level
Request unprotection of a page, or reducing the protection level
Request a specific to a protected page
Please request an edit directly on the protected page's talk page before posting here |
2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 |
Place requests for new or upgrading pending changes, semi-protection, full protection, move protection, create protection, template editor protection, or upload protection at the BOTTOM of this section. Check the archive of fulfilled and denied requests or, failing that, the page history if you cannot find your request. Only recently answered requests are still listed here.
Reason: Persistent changes to the player's club before an official transfer is announced and while there is a template that cautions against doing so. Vasil3fonov ( talk) 08:07, 4 July 2024 (UTC)
Semi-protection: requesting six-month semi in response to persistent sockpuppetry by the banned Australian Railroad IP. ~ Pbritti ( talk) 13:21, 4 July 2024 (UTC)
Temporary semi-protection: Persistent disruptive editing – Persistent disruptive editing by anonymous editor, likely editing outside of their account. livelikemusic ( TALK!) 13:46, 4 July 2024 (UTC)
Temporary semi-protection: Persistent disruptive editing – Persistent disruptive editing by anonymous editors. livelikemusic ( TALK!) 13:48, 4 July 2024 (UTC)
Temporary extended confirmed protection: Persistent disruptive editing – Persistent hijacking of redirect with WP:PROMO content for a non-notable company. Drm310 🍁 ( talk) 14:23, 4 July 2024 (UTC)
Reason: Persistent addition of unsourced content by IP editor. Ckfasdf ( talk) 14:51, 4 July 2024 (UTC)
Reason: WP:PIA Isi96 ( talk) 15:21, 4 July 2024 (UTC)
Reason: High level of IP disruption; all IP edits since the beginning of May have been disruptive. This article has, for some time now, been a magnet for apparent nationalistic POV-pushing on account of MG's current ownership. Sable232 ( talk) 15:25, 4 July 2024 (UTC)
Reason: Persistent vandalism by IP addresses and new accounts (all likely by the same person). JeffSpaceman ( talk) 15:48, 4 July 2024 (UTC)
Temporary extended confirmed protection: Persistent disruptive editing – Disruptive editing by IP hopper continues... ภץאคгöร 15:59, 4 July 2024 (UTC)
Indefinite template protection: High-risk template – Sync with parent. Sohom ( talk) 16:47, 4 July 2024 (UTC)
Reason: High level of ip vandalism Theonewithreason ( talk) 17:17, 4 July 2024 (UTC)
Indefinite semi-protection: Persistent disruptive editing – Including, but not limited to, a persistent date-changing vandal. – LaundryPizza03 ( d c̄) 17:25, 4 July 2024 (UTC)
Indefinite semi-protection: Persistent vandalism – Including, but not limited to, a persistent date-changing vandal. – LaundryPizza03 ( d c̄) 17:27, 4 July 2024 (UTC)
Indefinite semi-protection: Persistent disruptive editing – Including, but not limited to, a persistent date-changing vandal. – LaundryPizza03 ( d c̄) 17:27, 4 July 2024 (UTC)
Indefinite full protection: user doesnt want any messages. There have been some automated messages through twinkle and such so I think indef full would stop this per the user request of no messages. 48 JCL 17:32, 4 July 2024 (UTC)
Reason: Ongoing IP vandalism LucasR muteacc ( talk) 17:35, 4 July 2024 (UTC)
Reason: Disruptive Editing Ado1024 ( talk) 18:57, 4 July 2024 (UTC)
Reason: High level of IP vandalism. Kataadj ( talk) 19:26, 4 July 2024 (UTC)
Temporary semi-protection: Persistent disruptive editing – WP:DE by editors from Wikipedia:Sockpuppet investigations/Balakashyap, WP:LOUTSOCK. The article already exists in the redirect's location. Jeraxmoira🐉 ( talk) 19:34, 4 July 2024 (UTC)
Before posting, first discuss with the protecting admin at their talk page. Post below only if you receive no reply.
Check the archives if you cannot find your request. Only recently answered requests are still listed here.
Reason: Been protected 6+ years, lower activity, should we give unprotection a shot? Razorback250 ( talk) 01:24, 4 July 2024 (UTC)
Ideally, requests should be made on the article talk page rather than here.
{{
Edit protected}}
, {{
Edit template-protected}}
, {{
Edit extended-protected}}
, or {{
Edit semi-protected}}
to the article's talk page if you would like to make a change rather than requesting it here. Doing so will automatically place the page in the appropriate category for the request to be reviewed.{{
Edit COI}}
template should be used.
A historical archive of previous protection requests can be found at Wikipedia:Requests for page protection/Archive.