Zane Matthew

<p>Have you had to make a working project publicly accessible for your client, yet still have to keep<br />
the site “private” to the general public?</p>
<p><strong><a href="http://demo.zanematthew.com/client-access/" rel="nofollow ugc">Demo</a></strong></p>
<p>Normally you’ll quickly hack in an allowed IP list, server-side password (htpasswd), etc. Why hack this in? With Client Access you can take the professional approach. Use a WordPress plugin to allow specific IPs, or those with the universal password the ability to access the work in progress.</p>
<h4>Allow by IP</h4>
<p>Once enabled via the settings tab, you can add a list of IPs to the textarea. These IP addresses are the <em>only</em> IP addresses that are allowed. Additionally you can add a comment per IP to better detail each entry.</p>
<ul>
<li>Provide a list of IPs that are allowed</li>
<li>Comments are allowed for IPs</li>
<li>Display a content message</li>
<li>Display a footer message</li>
<li>All IPs are validated against the latest IP protocols</li>
</ul>
<p>Example:</p>
<pre><code>// Office at 123 Main street
192.168.0.1

// My localhost
127.0.0.1

// Ana
123.456.789
</code></pre>
<h4>Allow by Universal Password</h4>
<p>Once enabled via the settings tab, you can create a universal password that is <em>shared</em> with all users. No user name is required.</p>
<p>Anyone that visits the website while this is enabled will see the default message you’ve added. The site will only be accessible to users that you have shared out the password with.</p>
<ul>
<li>Provide a universal password</li>
<li>Set an expire time</li>
<li>Display a content message</li>
<li>Display a footer message</li>
</ul>
<h4>Allow By Role</h4>
<p>Allow by role of choice.</p>
<ul>
<li>Choose any registered role</li>
<li>Display a content message</li>
<li>Display a footer message</li>
</ul>
<h4>Translations</h4>
<ul>
<li><a href="http://www.echodesplugins.li-an.fr/" rel="nofollow ugc">French</a></li>
<li><a href="http://dianakolnik.com/" rel="nofollow ugc">Spanish</a></li>
</ul>


Client Access

Let your client see their work in progress.

Jeremy Felt

<p>Custom Posts Per Page allows you to specify how many posts are displayed per page depending on your current view. Once settings are changed, the <em>Blog pages show at most</em> setting in the <em>Reading</em> menu will be ignored.</p>
<p>Settings are available for:</p>
<ul>
<li>Home (Index) Page
<ul>
<li>As long as view is set to blog posts, not static page.</li>
</ul>
</li>
<li>Category Pages</li>
<li>Tag Pages</li>
<li>Author Pages</li>
<li>Archive Pages</li>
<li>Search Pages</li>
<li>Default Page (<em>Any page not covered above.</em>)</li>
<li>Custom Post Type archive pages
<ul>
<li>All Custom Post Types are detected automatically.</li>
</ul>
</li>
</ul>
<p>Each of the above settings can have a different value for the first page displayed <strong>and</strong> subsequent paged views.</p>
<p>Custom Posts Per Page makes it easy to manage exactly how your content is displayed to your readers, especially when different views have different layouts, rather than relying on the single setting in the Reading menu or having to hard code options in your custom theme.</p>


Custom Posts Per Page

Thank you so much for making this plugin!



Saved a lot of time and is a great addition

Custom Posts Per Page provides a settings page in your WordPress admin that allows you to specify how many posts are displayed for different views.

Client Access vs Custom Posts Per Page