Category:PBC pages with incorrect protection templates

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

This category has a backlog that requires the attention of willing editors. This notice will hide itself when this category has fewer than 20 items. (recount)

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

1. Remove any incorrect or expired protection templates from the page
2. 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.
3. 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. This 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
4. 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.