Stephanie Leary

<ul>
<li>Optionally adds private pages to <code>wp_list_pages()</code>, <code>wp_page_menu()</code>, and the Pages widget</li>
<li>Provides a separate <code>wp_list_private_pages()</code> tag (a clone of <code>wp_list_pages()</code> that accepts all the same arguments)</li>
<li>Specifies private categories, in which all posts will automatically be set to private</li>
<li>Lets you change the “Private:” prefix on private post/page titles</li>
<li>Lets you change the “Protected:” prefix on password-protected post/page titles</li>
<li>Lets you choose which user roles can read private pages and posts</li>
</ul>
<p>Now on <a href="https://github.com/sillybean/private-suite" rel="nofollow ugc">GitHub</a>.</p>
<h4>Translations</h4>
<ul>
<li>French (fr_FR) by Regis Lemaire</li>
<li>Bulgarian (bg_BG) by <a href="http://www.siteground.com/" rel="nofollow ugc">SiteGround</a></li>
<li>Turkish (tr_TR) by <a href="http://bijoubijouterie.com" rel="nofollow ugc">Ömer Faruk Karabulut</a></li>
</ul>
<h3>Notes</h3>
<h3>Reading Settings</h3>
<p>You must have at least one public page. Otherwise, as of 3.1, the front page settings (where you can choose a static page as your home page) will not appear on the settings page at all. As long as you have one public page, all the private pages will appear as options in the dropdown menu.</p>
<h3>Page Lists and Widgets</h3>
<p>Adding private pages to <code>wp_list_pages()</code>, <code>wp_page_menu()</code>, and the Pages widget does not always work as it should. The private pages will be out of order, and they might appear as children of the wrong parent page. If this occurs, try using the <code>wp_list_private_pages()</code> template tag instead. It’s a clone of <code>wp_list_pages()</code> and should accept all the same arguments. This plugin includes an extra Pages widget that includes private pages.</p>
<h3>Private Categories</h3>
<p>When you mark a category as private, all the posts in that category will have their visibility set to private when they are published, even if you don’t change the visibility setting on the edit screen. Only published posts are affected; your draft, pending, and scheduled posts will work as usual, except that scheduled posts will be set to private when they become active.</p>
<h3>Acknowledgments</h3>
<p>Huge thanks to <a href="https://profiles.wordpress.org/mtekk" rel="nofollow ugc">mtekk</a> for providing the <a href="https://core.trac.wordpress.org/ticket/8592" rel="nofollow ugc">patch</a> that makes the page list features possible. The alternative method of listing pages was adapted from <a href="http://activecodeline.com/create-a-menu-for-private-pages-and-posts-in-wordpress" rel="nofollow ugc">Branko Ajzele</a>.</p>
<h3>Translations</h3>
<p>If you would like to send me a translation, please write to me through <a href="http://sillybean.net/about/contact/" rel="nofollow ugc">my contact page</a>. Let me know which plugin you’ve translated and how you would like to be credited. I will write you back so you can attach the files in your reply.</p>


Private Suite

Allows you to choose who can read private content and offers better control of privacy features.

richard4339

cmwelsh

<p>A simple plugin for WordPress that redirects users to the login page whenever they try to visit any page/post/etc on the blog, with an option menu to turn this functionality on or off. When enabled, the entire blog essentially becomes a private blog.</p>
<h3>To Do</h3>
<ul>
<li>Nothing currently. If you have any requests, please submit them on <a href="https://github.com/richard4339/wp-require-login/issues" rel="nofollow ugc">GitHub</a>.</li>
</ul>
<h3>Git/Subversion</h3>
<p>In addition to the subversion access that WordPress is providing, this plugin is available through git at <a href="https://github.com/richard4339/wp-require-login" rel="nofollow ugc">GitHub</a>.</p>


Require Login

A plugin for Wordpress that redirects users to the login page whenever they try to visit any page/post/etc on the blog.

Private Suite vs Require Login