Make WordPress Core

Opened 7 years ago

Closed 6 years ago

Last modified 6 years ago

#7862 closed defect (bug) (worksforme)

Password protected page not prompting for password when designated the Posts Page

Reported by: MichaelH Owned by:
Milestone: Priority: normal
Severity: minor Version: 2.6.1
Component: General Keywords:
Focuses: Cc:


A visitor is not prompted for a password when they navigate to a page that is password protected, and that page is designated as the Posts Page in Settings->Reading->Front page displays->A static page.

Reported by Nic S in the forums:

Change History (8)

#1 @Denis-de-Bernardy
6 years ago

  • Keywords needs-patch added
  • Milestone set to 2.8
  • Severity changed from normal to minor

the page template is ignored too

#2 @janeforshort
6 years ago

  • Milestone changed from 2.8 to Future Release

Punting due to feature freeze. Reconsider with next release.

#3 @Denis-de-Bernardy
6 years ago

  • Resolution set to invalid
  • Status changed from new to closed

Closing this as invalid. It's easy enough to change the template with a plugin. Enforcing the password could be done on the template_redirect hook.

#4 @DD32
6 years ago

Re-opening due to it being a bug, While you can achieve anything with a plugin, No need to require bug fixing via a plugin, esp when its core functionality which may be hard to achieve.

Page templates are ignored & so is the password option.

#5 @DD32
6 years ago

  • Resolution invalid deleted
  • Status changed from closed to reopened

#6 @DD32
6 years ago

  • Keywords needs-patch removed
  • Milestone Future Release deleted
  • Resolution set to worksforme
  • Status changed from reopened to closed

..Except that password protected pages require a password, And it abides by the Template option.

#7 @Denis-de-Bernardy
6 years ago

@DD32: What the reporter is meaning/wanting is that setting a password for the static page that is used to display the blog will have no effect.

It's still invalid, though. I considered contributing the needed patch, but it then occurred to me that it involved a workflow change that is large enough to make it plugin material.

#8 @DD32
6 years ago

Oh... Right, The Posts page, Not a Page set as the front page..

In that case, You're right, It was invalid - as its not a workflow which WordPress uses.

Theres another theme file which can be used for the posts page, making the template part moot, and as for the password, The page is never loaded, just used as a place holder, so password-protection is not required.

If password-protection is needed for the entire blog, or posts, then a better solution from a plugin would be best.

Note: See TracTickets for help on using tickets.