Zane Matthew

Have you had to make a working project publicly accessible for your client, yet still have to keep 
the site “private” to the general public?
<a href="http://demo.zanematthew.com/client-access/" rel="nofollow ugc">Demo</a>
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.
<h4>Allow by IP</h4>
Once enabled via the settings tab, you can add a list of IPs to the textarea. These IP addresses are the only IP addresses that are allowed. Additionally you can add a comment per IP to better detail each entry.
<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>
Example:
<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>
Once enabled via the settings tab, you can create a universal password that is shared with all users. No user name is required.
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.
<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>
Allow by role of choice.
<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.

Sparanoid

Relative URL applies the <code>wp_make_link_relative</code> function to links (posts, categories, pages, etc.) to convert them to relative URLs. Useful for developers when debugging local WordPress instance on a mobile device (iPad, iPhone, etc.).
Notice: This plugin SHOULD be used for local development only. I haven’t tested on a production environment; it may work with some issues, like unwanted URLs in RSS feed or sharing URLs are replaced with relative URLs, etc.
More information please visit my <a href="https://sparanoid.com/work/relative-url/" rel="nofollow ugc">site</a>.
For example:
<pre><code>http://localhost:8080/wp/
</code></pre>
Will be converted to:
<pre><code>/wp/
</code></pre>
And..
<pre><code>http://localhost:8080/wp/2012/09/01/hello-world/
</code></pre>
Will be converted to:
<pre><code>/wp/2012/09/01/hello-world/
</code></pre>
And..
<pre><code>http://localhost:8080/wp/wp-content/themes/twentyeleven/style.css
</code></pre>
Will be converted to:
<pre><code>/wp/wp-content/themes/twentyeleven/style.css
</code></pre>
Then after activating this plugin, you can simply access your local instance using <code>http://10.0.1.5:8888/wp/</code> on your iPad or other mobile devices without having styles and navigation issue.

Relative URL

Relative URL applies wp_make_link_relative function to links to convert them to relative URLs.

Client Access vs Relative URL