fullthrottledevelopment

Glenn Ansley

This plugin does one thing. If a page that is password protected has children pages, all children pages will be protected with the same password.
If the correct password is entered on the parent page or any of its children pages, all related pages will be viewable to the user.
The plugin protects unlimited levels of grandchildren pages via the $post->ancestors. It uses first ancestor that is password protected.
<h3>Additional Information</h3>
The plugin currently works by looking for parent pages that are password protected and applying the same restrictions the the currently being viewed child page. This means that the children pages do not actually get a password added to the database.
I’m trying to decide if this is the best way to proceeed or if I should take another route (such as adding / updating / removing passwords from children pages at the write or save post screen).
Please feel free to offer any suggestions or report any bugs here: [http://fullthrottledevelopment.com/password-protect-children-pages/]
Thanks!

FT Password Protect Children Pages

Applies the same protection to children pages applied to the parent page.

Julio Potier

You can now add passwords as many as you need on every protected page.
Why? Because you can protect page and give your client a personnal password, not just a random pasword or everyone.
Option: If you are logged as admin or the page’s author, you won’t need to enter password.
Option: If you set a list of child pages, just change any password (parent page or any child) and all the password for the hierarchy will be updated!

Multiple Passwords for Protected Pages

Add more than 1 password to your protected pages, also administrators and page's authors can view the protected pages without password.

FT Password Protect Children Pages vs Multiple Passwords for Protected Pages