Category:Pages with incorrect protection templates

This is a maintenance category, used for the maintenance of BTW. It is not part of the encyclopedia and contains non-article pages, or groups articles by status rather than subject. Do not include this category in content categories.

This is a hidden category. It is not shown on its member pages, unless the corresponding user preference (appearance → show hidden categories) is set.

Shortcut

WP:IPT

Administrators: Please do not delete this category as empty!
This category may be empty occasionally or even most of the time.

These pages are automatically listed here, using the {{PROTECTIONLEVEL}} magic word, when their protection status does not correspond with the protection template used on them.

Remedies

Remove any incorrect or expired protection templates from the page
1. Keep in mind that moving pages is locked to autoconfirmed by default, meaning {{pp-move}} is considered invalid on pages that are autoconfirmed move protected and should also be removed.
Often, a page will not contain the invalid protection template directly, but rather will inherit it from a template which is transcluded on it. This often happens when the template is protected, but the protection template used for that template is not wrapped in <noinclude>...</noinclude> tags. To fix this problem:
1. if the template uses either {{documentation}} or {{collapsible option}}, that will display any lock icon that is appropriate, so simply remove the protection template;
2. otherwise, move the protection template within <noinclude></noinclude> tags,
  Note that the pages that link to the template via transclusion will not be removed from this category immediately, depending on the job queue, but it should resolve itself automatically. Alternatively, you can null edit the page for immediate results.
3. if the page is a redirect on which the {{Redirect category shell}} template is transcluded, check the expiry date to see if protection expires later that same day. If the expiry date is the same day, then the redirect will automatically fall out of this category later that day. If the expiry date is not the same day, then a null edit should fix the situation.
If a page has the correct template yet still appears in this category, it could be a problem with the |expiry= parameter of the protection template. Nowadays, the actual expiry time is automatically detected, so the remedy for problems like this is to remove the |expiry= parameter. Historically, the cause could be one or more of:
1. the wrong date format was used
2. it indicates a date in the past (commonly encountered when protection expires and is later reinstated without updating the protection template)
3. it has the correct date but lacks a time - dates without times are treated as midnight
If the page contains the correct protection template in a proper date format but is still in this category, a null edit should fix the situation.