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.

nuagelab

<p>This plugin automatically detects a domain name change, and updates all the WordPress tables in the database to reflect this change.</p>
<h4>Features</h4>
<ul>
<li>Easily migrate a WordPress site from one domain to another</li>
<li>Migrate www.domain.com and domain.com at once</li>
<li>Migrate http and https links at once</li>
</ul>
<h4>Feedback</h4>
<ul>
<li>We are open for your suggestions and feedback – Thank you for using or trying out one of our plugins!</li>
<li>Drop us a line <a href="http://twitter.com/#!/nuagelab" rel="nofollow ugc">@nuagelab</a> on Twitter</li>
<li>Follow us on <a href="https://www.facebook.com/pages/NuageLab/150091288388352" rel="nofollow ugc">our Facebook page</a></li>
<li>Drop us a line at <a href="mailto:wordpress-plugins@nuagelab.com" rel="nofollow ugc">wordpress-plugins@nuagelab.com</a></li>
</ul>
<h4>More</h4>
<ul>
<li><a href="http://www.nuagelab.com/products/wordpress-plugins/" rel="nofollow ugc">Also see our other plugins</a> or see <a href="https://profiles.wordpress.org/users/nuagelab/" rel="nofollow ugc">our WordPress.org profile page</a></li>
</ul>
<h3>Translations</h3>
<ul>
<li>English</li>
<li>French</li>
<li>Spanish</li>
<li>Slovak</li>
</ul>


Automatic Domain Changer

Not useful with large rules causing errors with large rules that bypass the 1 GB

Not useful with large rules

Automatically detects a domain name change, and updates all the WordPress tables in the database to reflect this change.

Client Access vs Automatic Domain Changer