<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>zeo &#187; private</title>
	<atom:link href="http://zeo.unic.net.my/tag/private/feed/" rel="self" type="application/rss+xml" />
	<link>http://zeo.unic.net.my</link>
	<description>Safirul Alredha on web, WordPress, K2, Apple, ...</description>
	<lastBuildDate>Thu, 02 Jun 2011 01:31:06 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
		<item>
		<title>Password Protected WordPress blog</title>
		<link>http://zeo.unic.net.my/password-protected-wordpress-blog/</link>
		<comments>http://zeo.unic.net.my/password-protected-wordpress-blog/#comments</comments>
		<pubDate>Fri, 29 Sep 2006 15:07:38 +0000</pubDate>
		<dc:creator>zeo</dc:creator>
				<category><![CDATA[WordPress]]></category>
		<category><![CDATA[password]]></category>
		<category><![CDATA[private]]></category>

		<guid isPermaLink="false">http://zeo.unic.net.my/notes/password-protected-wordpress-blog/</guid>
		<description><![CDATA[Sometimes I receive some weird request regarding WordPress blog customization. This time a client wanted to password protected the entire blog and not specific post. Basically, you can use Apache User Authentication but there&#8217;s another way to do this in WordPress. Go to Users &#8594; Authors &#38; Users sub-panel. Add a new user in the [...]]]></description>
			<content:encoded><![CDATA[<p>Sometimes I receive some weird request regarding WordPress blog customization. This time a client wanted to password protected the entire blog and not specific post. Basically, you can use <a rel="nofollow" href="http://httpd.apache.org/docs/1.3/howto/auth.html">Apache User Authentication</a> but there&#8217;s another way to do this in WordPress.</p>
<ol>
<li>Go to Users &rarr; Authors &amp; Users sub-panel.</li>
<li>Add a new user in the <a rel="nofollow" href="http://codex.wordpress.org/Users_Authors_and_Users_SubPanel#Add_New_User">Add New User</a> section. This login will be used to access your WordPress by other user. Or go to Settings &rarr; General &rarr; Membership and check &#8220;Anyone can register&#8221;.</li>
<li>Add the following lines to your WordPress Theme&#8217;s template <a rel="nofollow" href="http://codex.wordpress.org/Theme_Development#Functions_File"><tt>functions.php</tt></a> file (For example, <tt>functions.php</tt> file for a Theme named &#8220;default&#8221; would probably reside in the directory <tt>wp-content/themes/default/functions.php</tt>) or create it as a Plugin by filling the additional <a rel="nofollow" href="http://codex.wordpress.org/Writing_a_Plugin#Standard_Plugin_Information">Standard Plugin Information</a>:
<pre>
&lt;?php
function password_protected() {
	if ( !is_user_logged_in() )
		auth_redirect();
}

add_action('login_head', 'rsd_link');
add_action('login_head', 'wlwmanifest_link');
add_action('template_redirect', 'password_protected');
add_action('do_feed', 'password_protected');
?&gt;
</pre>
</li>
<li>Go to Settings &rarr; Discussion sub-panel. Under Default article settings, uncheck &#8220;Attempt to notify any blogs linked to from the article (slows down posting.)&#8221;.</li>
<li>Finally, go to Settings &rarr; Privacy and set &#8220;Blog Visibility to I would like to block search engines, but allow normal visitors&#8221;. Click Save Changes.</li>
</ol>
<p>Now visitors will be asked to log in using WordPress login form to view your WordPress blog / site. This is very suitable for someone that wanted privacy or owned a private password protected WordPress blog / site.</p>
]]></content:encoded>
			<wfw:commentRss>http://zeo.unic.net.my/password-protected-wordpress-blog/feed/</wfw:commentRss>
		<slash:comments>37</slash:comments>
		</item>
	</channel>
</rss>

