Glenn Ansley

fullthrottledevelopment

<p>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.</p>
<p>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.</p>
<p>The plugin protects unlimited levels of grandchildren pages via the $post->ancestors. It uses first ancestor that is password protected.</p>
<h3>Additional Information</h3>
<p>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.</p>
<p>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).</p>
<p>Please feel free to offer any suggestions or report any bugs here: [http://fullthrottledevelopment.com/password-protect-children-pages/]</p>
<p>Thanks!</p>


FT Password Protect Children Pages

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

<p>Once activated, private posts will no longer have the word “Private: ” appended to the beginning of their title.</p>
<h4>Version History</h4>
<ul>
<li>0.1 – Original release.</li>
</ul>


FT Remove Private From Post Titles

Once activated, private posts will no longer have the word "Private: " appended to the beginning of their title.

FT Password Protect Children Pages vs FT Remove Private From Post Titles