<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Password Protect More Than the_content()</title>
	<atom:link href="http://digwp.com/2009/08/password-protect-more-than-the_content/feed/" rel="self" type="application/rss+xml" />
	<link>http://digwp.com/2009/08/password-protect-more-than-the_content/</link>
	<description>Take your WordPress skills to the next level.</description>
	<lastBuildDate>Tue, 15 May 2012 08:36:23 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Robin</title>
		<link>http://digwp.com/2009/08/password-protect-more-than-the_content/#comment-2244</link>
		<dc:creator>Robin</dc:creator>
		<pubDate>Tue, 03 Nov 2009 13:54:16 +0000</pubDate>
		<guid isPermaLink="false">http://digwp.com/?p=531#comment-2244</guid>
		<description>I have some password-protected pages and I allow comments to be made by people who know the password.  So far, so good.  But I also have a &quot;Recent Comments&quot; widget in my sidebar, and that allows people who don&#039;t have the password to see comments on password-protected pages.  Can this be rectified?</description>
		<content:encoded><![CDATA[<p>I have some password-protected pages and I allow comments to be made by people who know the password.  So far, so good.  But I also have a &#8220;Recent Comments&#8221; widget in my sidebar, and that allows people who don&#8217;t have the password to see comments on password-protected pages.  Can this be rectified?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bob tomorrowland</title>
		<link>http://digwp.com/2009/08/password-protect-more-than-the_content/#comment-2075</link>
		<dc:creator>bob tomorrowland</dc:creator>
		<pubDate>Tue, 20 Oct 2009 20:02:11 +0000</pubDate>
		<guid isPermaLink="false">http://digwp.com/?p=531#comment-2075</guid>
		<description>Do you know of a Wordpress plugin that allows me to password-protect my posts for multiple users? In this scenario, one user would have a password to give them access to certain posts, while another user has a different password to see a different set of posts. Is this even possible?

Many thanks!

/Bob</description>
		<content:encoded><![CDATA[<p>Do you know of a WordPress plugin that allows me to password-protect my posts for multiple users? In this scenario, one user would have a password to give them access to certain posts, while another user has a different password to see a different set of posts. Is this even possible?</p>
<p>Many thanks!</p>
<p>/Bob</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Arni</title>
		<link>http://digwp.com/2009/08/password-protect-more-than-the_content/#comment-2015</link>
		<dc:creator>Arni</dc:creator>
		<pubDate>Fri, 16 Oct 2009 23:38:31 +0000</pubDate>
		<guid isPermaLink="false">http://digwp.com/?p=531#comment-2015</guid>
		<description>Where exactly do I put the php-function in the update-box?</description>
		<content:encoded><![CDATA[<p>Where exactly do I put the php-function in the update-box?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Susek</title>
		<link>http://digwp.com/2009/08/password-protect-more-than-the_content/#comment-1801</link>
		<dc:creator>John Susek</dc:creator>
		<pubDate>Tue, 29 Sep 2009 17:19:30 +0000</pubDate>
		<guid isPermaLink="false">http://digwp.com/?p=531#comment-1801</guid>
		<description>I wanted to password protect a custom page template (for use with the Pods CMS in my case). This snippet is working great for me:

&lt;code&gt;&lt;?php&lt;/code&gt;
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&lt;code&gt;if ( post_password_required() ) {&lt;/code&gt;
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&lt;code&gt;echo get_the_password_form();&lt;/code&gt;
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&lt;code&gt;}&lt;/code&gt;
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&lt;code&gt;else {&lt;/code&gt;
&lt;code&gt;?&gt;&lt;/code&gt;

.. your custom php code or whatever ..

&lt;code&gt;&lt;?php&lt;/code&gt;
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&lt;code&gt;}&lt;/code&gt;
&lt;code&gt;?&gt;&lt;/code&gt;

Quick easy way to password protect any content in your templates.</description>
		<content:encoded><![CDATA[<p>I wanted to password protect a custom page template (for use with the Pods CMS in my case). This snippet is working great for me:</p>
<p><code>&lt;?php</code><br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<code>if ( post_password_required() ) {</code><br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<code>echo get_the_password_form();</code><br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<code>}</code><br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<code>else {</code><br />
<code>?&gt;</code></p>
<p>.. your custom php code or whatever ..</p>
<p><code>&lt;?php</code><br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<code>}</code><br />
<code>?&gt;</code></p>
<p>Quick easy way to password protect any content in your templates.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Coyier</title>
		<link>http://digwp.com/2009/08/password-protect-more-than-the_content/#comment-1417</link>
		<dc:creator>Chris Coyier</dc:creator>
		<pubDate>Mon, 24 Aug 2009 22:02:40 +0000</pubDate>
		<guid isPermaLink="false">http://digwp.com/?p=531#comment-1417</guid>
		<description>Uh yeah that&#039;s WAY easier. I had no idea this function existed. I just tested it out on a site I was using the technique in this article and it worked great. I&#039;ll update the article.</description>
		<content:encoded><![CDATA[<p>Uh yeah that&#8217;s WAY easier. I had no idea this function existed. I just tested it out on a site I was using the technique in this article and it worked great. I&#8217;ll update the article.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jay</title>
		<link>http://digwp.com/2009/08/password-protect-more-than-the_content/#comment-1397</link>
		<dc:creator>Jay</dc:creator>
		<pubDate>Sun, 23 Aug 2009 20:29:28 +0000</pubDate>
		<guid isPermaLink="false">http://digwp.com/?p=531#comment-1397</guid>
		<description>&lt;code&gt;if ( !post_password_required() ) { echo &#039;protected stuff&#039;; }&lt;/code&gt;

That works great for me :)</description>
		<content:encoded><![CDATA[<p><code>if ( !post_password_required() ) { echo 'protected stuff'; }</code></p>
<p>That works great for me :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Coyier</title>
		<link>http://digwp.com/2009/08/password-protect-more-than-the_content/#comment-1366</link>
		<dc:creator>Chris Coyier</dc:creator>
		<pubDate>Wed, 19 Aug 2009 13:00:03 +0000</pubDate>
		<guid isPermaLink="false">http://digwp.com/?p=531#comment-1366</guid>
		<description>That&#039;s interesting I&#039;ll have to give that a shot. 

Protecting using PHP via the template itself is clearly a better solution. The above was manufactured in a pinch when I didn&#039;t see any other way of getting it done.</description>
		<content:encoded><![CDATA[<p>That&#8217;s interesting I&#8217;ll have to give that a shot. </p>
<p>Protecting using PHP via the template itself is clearly a better solution. The above was manufactured in a pinch when I didn&#8217;t see any other way of getting it done.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben</title>
		<link>http://digwp.com/2009/08/password-protect-more-than-the_content/#comment-1362</link>
		<dc:creator>Ben</dc:creator>
		<pubDate>Wed, 19 Aug 2009 07:57:16 +0000</pubDate>
		<guid isPermaLink="false">http://digwp.com/?p=531#comment-1362</guid>
		<description>I think a good improvement in WordPress would be to improve the password protection and make it more versatile.

I wrote an article recently about creating a members category protected by login: &lt;a href=&quot;http://wordpressthemescollection.com/the-almost-ultimate-members-page-in-wordpress-182.html&quot; rel=&quot;nofollow&quot;&gt;
The (almost) ultimate members page in WordPress&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>I think a good improvement in WordPress would be to improve the password protection and make it more versatile.</p>
<p>I wrote an article recently about creating a members category protected by login: <a href="http://wordpressthemescollection.com/the-almost-ultimate-members-page-in-wordpress-182.html" rel="nofollow"><br />
The (almost) ultimate members page in WordPress</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://digwp.com/2009/08/password-protect-more-than-the_content/#comment-1361</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Wed, 19 Aug 2009 07:27:53 +0000</pubDate>
		<guid isPermaLink="false">http://digwp.com/?p=531#comment-1361</guid>
		<description>I think your Javascript approach isn&#039;t such a good idea: Protected content will be indexed by search engines.
Did you think of a solution like this one:

&lt;code&gt;$my_id = 7; //current post&#039;s id&lt;/code&gt;
&lt;code&gt;$post_data = get_post($my_id); //get current post&#039;s content (maybe that&#039;s already defined inside the loop, don&#039;t remember&lt;/code&gt;
&lt;code&gt;$is_protected = ($post_data-&gt;post_password != &#039;&#039;) ? true : false;&lt;/code&gt;

You can use &lt;code&gt;$is_protected&lt;/code&gt; within the template (for protecting custom fields) or filtering the post with the hook the_content. Give the filter a high number for priority (which means that it actually has a low priority) so you filter also changes made by other plugins.</description>
		<content:encoded><![CDATA[<p>I think your Javascript approach isn&#8217;t such a good idea: Protected content will be indexed by search engines.<br />
Did you think of a solution like this one:</p>
<p><code>$my_id = 7; //current post's id</code><br />
<code>$post_data = get_post($my_id); //get current post's content (maybe that's already defined inside the loop, don't remember</code><br />
<code>$is_protected = ($post_data-&gt;post_password != '') ? true : false;</code></p>
<p>You can use <code>$is_protected</code> within the template (for protecting custom fields) or filtering the post with the hook the_content. Give the filter a high number for priority (which means that it actually has a low priority) so you filter also changes made by other plugins.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

