<?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>DAP Documentation &#187; WordPress Plugins</title>
	<atom:link href="http://www.digitalaccesspass.com/doc/category/wordpress-plugins/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.digitalaccesspass.com/doc</link>
	<description>Documentation for DigitalAccessPass.com</description>
	<lastBuildDate>Mon, 26 Jul 2010 23:59:30 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Protecting Videos</title>
		<link>http://www.digitalaccesspass.com/doc/protecting-videos/</link>
		<comments>http://www.digitalaccesspass.com/doc/protecting-videos/#comments</comments>
		<pubDate>Mon, 24 May 2010 18:12:05 +0000</pubDate>
		<dc:creator>Ravi Jayagopal</dc:creator>
				<category><![CDATA[3rd Party Integration]]></category>
		<category><![CDATA[Access Control]]></category>
		<category><![CDATA[FAQ]]></category>
		<category><![CDATA[File Resources]]></category>
		<category><![CDATA[Plugins]]></category>
		<category><![CDATA[Protecting Content]]></category>
		<category><![CDATA[Protection FAQ]]></category>
		<category><![CDATA[Video]]></category>
		<category><![CDATA[WordPress Plugins]]></category>

		<guid isPermaLink="false">http://www.digitalaccesspass.com/doc/?p=412</guid>
		<description><![CDATA[There are many ways in which you can protect videos.
Case 1: The video file is stored on your web site
By default, DAP can only protect files that are stored on the same web site where DAP is installed.
So if you install DAP on YourSite.com , then your files must also be located on YourSite.com. DAP [...]]]></description>
			<content:encoded><![CDATA[<p>There are many ways in which you can protect videos.</p>
<h3>Case 1: The video file is stored on your web site</h3>
<p>By default, DAP can only protect files that are stored on the same web site where DAP is installed.</p>
<p>So if you install DAP on <strong>YourSite.com</strong> , then your files must also be located on <strong>YourSite.com</strong>. DAP installed on <strong>YourSite.com</strong> cannot protect files (.mp4, .mp3, .html, .pdf, .doc) that are stored on <strong>AnotherSite.com</strong>.</p>
<p>So assuming the files are stored on the same site as DAP, you can (and should) protect both the <strong>actual video file</strong>, as well as the <strong>blog post or page in which the embed-code</strong> for your video is published, by adding both to a Product.</p>
<p>This gives you 2 levels of protection for your videos:</p>
<p><strong>Level 1</strong>: The blog post or page containing the video player code, itself is accessible only by authorized members.<br />
<strong>Level 2</strong>: When an authorized user gets legitimate access to the page where the video is published (because they&#8217;re a paying member, say), even if they try to do a view source and figure out the location of the video (eg., <em>http://yoursite.com/videos/howtovideo1.mp4</em>) , and pass it around by email to their friends (or post the link in an online forum), their friends still can&#8217;t view the video, because the video link itself is protected by DAP.</p>
<p>If you have some text that you want the casual visitor (and Google) to read, but wish to protect only the video, then you could turn Sneak-Peek on (in <strong>Setup</strong> &gt; <strong>Config</strong> &gt; <strong>Advanced</strong>), insert a WordPress more tag (&lt;!&#8211;more&#8211;&gt;) into your post just where you want the content to start being protected, and put the video player&#8217;s embed code after the <em>more</em> tag.</p>
<h3>Case 2: Video file is stored on Amazon S3</h3>
<p>The only 3rd-party-stored video files that DAP can protect at this time are videos (and other files) that are stored on Amazon S3. DAP cannot do this by itself, but uses a special WordPress plugin called <strong><a href="http://S3MediaVault.com" target="_blank">S3MediaVault.com</a></strong> , which is a plugin we developed specifically to make Amazon S3 videos play in your WordPress blog posts/pages. So again you get 2 levels of protection for your videos&#8230;</p>
<p><strong>Level 1</strong>: DAP protects the post/page where the special S3MV video player code is embedded<br />
<strong>Level 2</strong>: The S3MediaVault plugin makes sure that even if someone tried to do a view source and figure out the actual link to your Amazon S3 video, they still won&#8217;t be able to view the video.</p>
<h3>WARNING: Video stored on other 3rd party video sites</h3>
<p>DAP cannot protect, say, videos that are embedded from other 3rd party web sites like YouTube or Hulu. Of course, DAP can always protect the blog post or page itself that contains the video, but once an authorized user gets valid access to that blog page, they can see that it is a YouTube video (say), and then pass that YouTube video link to their friends, in which case DAP cannot protect that external YouTube video link.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.digitalaccesspass.com/doc/protecting-videos/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Customizing Login Widget</title>
		<link>http://www.digitalaccesspass.com/doc/customizing-login-widget/</link>
		<comments>http://www.digitalaccesspass.com/doc/customizing-login-widget/#comments</comments>
		<pubDate>Fri, 21 May 2010 16:25:19 +0000</pubDate>
		<dc:creator>Ravi Jayagopal</dc:creator>
				<category><![CDATA[Customization]]></category>
		<category><![CDATA[Plugins]]></category>
		<category><![CDATA[Widgets]]></category>
		<category><![CDATA[WordPress]]></category>
		<category><![CDATA[WordPress Plugins]]></category>

		<guid isPermaLink="false">http://www.digitalaccesspass.com/doc/?p=408</guid>
		<description><![CDATA[Here&#8217;s how you can customize the HTML, look &#38; feel of the DAP Sidebar Login Widget.
There is a file in the following folder&#8230;
/wp-content/plugins/DAP-WP-LiveLinks/
by name&#8230;
DAP-WP-LoginForm-LoginLogout.html
Make a copy of that file on your desktop, rename it to&#8230;
customDAP-WP-LoginForm-LoginLogout.html
(just added the text &#8220;custom&#8221; at the front of the original file&#8217;s name).
You can then modify this new file however you [...]]]></description>
			<content:encoded><![CDATA[<p>Here&#8217;s how you can customize the HTML, look &amp; feel of the DAP Sidebar Login Widget.</p>
<p>There is a file in the following folder&#8230;</p>
<blockquote><p><strong>/wp-content/plugins/DAP-WP-LiveLinks/</strong></p></blockquote>
<p>by name&#8230;</p>
<blockquote><p><strong>DAP-WP-LoginForm-LoginLogout.html</strong></p></blockquote>
<p>Make a copy of that file on your desktop, rename it to&#8230;</p>
<blockquote><p><strong><span style="color: #ff0000;">custom</span>DAP-WP-LoginForm-LoginLogout.html</strong></p></blockquote>
<p>(just added the text &#8220;<span style="color: #ff0000;"><strong>custom</strong></span>&#8221; at the front of the original file&#8217;s name).</p>
<p>You can then modify this new file however you want, including altering spacing, and that&#8217;s what will be displayed.</p>
<p>Just be careful what you change &#8211; do not modify the field names or the submit URL. Feel free to change other visual elements.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.digitalaccesspass.com/doc/customizing-login-widget/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Forum Integration</title>
		<link>http://www.digitalaccesspass.com/doc/forum-integration/</link>
		<comments>http://www.digitalaccesspass.com/doc/forum-integration/#comments</comments>
		<pubDate>Sat, 27 Feb 2010 23:13:59 +0000</pubDate>
		<dc:creator>Ravi Jayagopal</dc:creator>
				<category><![CDATA[3rd Party Integration]]></category>
		<category><![CDATA[Access Control]]></category>
		<category><![CDATA[Config]]></category>
		<category><![CDATA[Forums]]></category>
		<category><![CDATA[Setup]]></category>
		<category><![CDATA[Users]]></category>
		<category><![CDATA[WordPress]]></category>
		<category><![CDATA[WordPress Plugins]]></category>

		<guid isPermaLink="false">http://www.digitalaccesspass.com/doc/?p=307</guid>
		<description><![CDATA[DAP currently integrates only with WordPress-based Forums &#8211; like bbPress, Simple:Press, etc.
What this essentially achieves, is that once your forum plugin has been integrated with DAP (explained below), anyone who is a member in your DAP-powered membership site, will also be automatically be logged in to your forum when they log in to your membership [...]]]></description>
			<content:encoded><![CDATA[<p>DAP currently integrates only with WordPress-based Forums &#8211; like bbPress, Simple:Press, etc.</p>
<p>What this essentially achieves, is that once your forum plugin has been integrated with DAP (explained below), anyone who is a member in your DAP-powered membership site, will also be automatically be logged in to your forum when they log in to your membership site.</p>
<p><strong>So they won&#8217;t have to log in twice</strong> [like, once into DAP and once into your forum].</p>
<p>Here&#8217;s how you set up the DAP/forum integration.</p>
<ol>
<li>Download the 3rd party wordpress forum plugin</li>
<li>Install it as per their instructions. We don&#8217;t support the installation or setup of the forum plugin itself.</li>
<li>Log in to your DAP Admin Dashboard and click on &#8220;Config &gt; Advanced&#8221;.</li>
<li>You have two settings on the page that applies to forum integration:<br />
&#8220;<strong>Sync DAP User data and WP User data</strong>&#8221;<br />
&#8220;<strong>Sync WP data only for PAID users</strong>&#8220;.(Both are explained further below.)</li>
<li>Pick &#8220;Y&#8221; or &#8220;N&#8221; for each of them, and you&#8217;re all set.</li>
</ol>
<p>First, a quick explanation of both settings.</p>
<h3>1) Sync DAP User data and WP User data</h3>
<p>If you turn this to &#8220;Y&#8221; (for &#8220;Yes&#8221;), then every time someone logs into DAP, they&#8217;re automatically logged into WordPress too (with a &#8220;User&#8221; role). And because they&#8217;re logged into WordPress, that means they&#8217;re also logged into your forum (because you are using a WordPress-based Forum Plugin which already integrates with your WordPress blog.)</p>
<h3>2) Sync WP data only for PAID users</h3>
<p>This one matters only if you have set (1) above to &#8220;Y&#8221;.</p>
<p>So once you have decided to turn on the DAP/Forum plugin integration, then if you want <strong>only your &#8220;PAID&#8221; members</strong> to have access to the forum, then set this to &#8220;Y&#8221;.</p>
<p>If you don&#8217;t care about both FREE and PAID users accessing your forum, then set this to &#8220;N&#8221;.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.digitalaccesspass.com/doc/forum-integration/feed/</wfw:commentRss>
		<slash:comments>18</slash:comments>
		</item>
		<item>
		<title>Upgrading to the latest version of LiveLinks</title>
		<link>http://www.digitalaccesspass.com/doc/upgrading-to-latest-version-livelinks/</link>
		<comments>http://www.digitalaccesspass.com/doc/upgrading-to-latest-version-livelinks/#comments</comments>
		<pubDate>Sun, 15 Mar 2009 21:33:43 +0000</pubDate>
		<dc:creator>Ravi Jayagopal</dc:creator>
				<category><![CDATA[LiveLinks]]></category>
		<category><![CDATA[Updates]]></category>
		<category><![CDATA[WordPress Plugins]]></category>

		<guid isPermaLink="false">http://www.digitalaccesspass.com/doc/?p=43</guid>
		<description><![CDATA[1) Download the latest version of DAP WP Livelinks from the members area.

2) Unzip the zip file to your desktop. Upload the entire DAP-WP-LiveLinks folder (including the folder too) to your WordPress plugins directory (which is wp-content/plugins/)
That&#8217;s it!
]]></description>
			<content:encoded><![CDATA[<p>1) Download the latest version of <strong>DAP WP Livelinks </strong>from the <a href="http://www.DigitalAccessPass.com/dap/">members area</a><strong>.<br />
</strong></p>
<p>2) Unzip the zip file to your desktop. Upload the entire <strong>DAP-WP-LiveLinks</strong> folder (including the folder too) to your WordPress plugins directory (which is <code>wp-content/plugins/</code>)</p>
<p>That&#8217;s it!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.digitalaccesspass.com/doc/upgrading-to-latest-version-livelinks/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Creating A Login Page Within WordPress</title>
		<link>http://www.digitalaccesspass.com/doc/creating-a-login-page-within-wordpress/</link>
		<comments>http://www.digitalaccesspass.com/doc/creating-a-login-page-within-wordpress/#comments</comments>
		<pubDate>Mon, 09 Mar 2009 19:26:02 +0000</pubDate>
		<dc:creator>Ravi Jayagopal</dc:creator>
				<category><![CDATA[Access Control]]></category>
		<category><![CDATA[Config]]></category>
		<category><![CDATA[Customization]]></category>
		<category><![CDATA[FAQ]]></category>
		<category><![CDATA[Personalization]]></category>
		<category><![CDATA[Protection FAQ]]></category>
		<category><![CDATA[WordPress]]></category>
		<category><![CDATA[WordPress FAQ]]></category>
		<category><![CDATA[WordPress Plugins]]></category>

		<guid isPermaLink="false">http://www.digitalaccesspass.com/doc/?p=38</guid>
		<description><![CDATA[Now DAP already provides you with a built-in login form, at YourSite.com/dap/login.php
But if you want to put this form &#8220;within&#8221; your WordPress blog, so as to give your login form the same Look &#38; Feel as the rest of your blog, all you need to do, is&#8230;
1) Create a WordPress “Page” (not &#8216;post&#8217;) with the [...]]]></description>
			<content:encoded><![CDATA[<p>Now DAP already provides you with a built-in login form, at <span style="color: #0000ff;">YourSite.com/dap/login.php</span></p>
<p>But if you want to put this form &#8220;within&#8221; your WordPress blog, so as to give your login form the same Look &amp; Feel as the rest of your blog, all you need to do, is&#8230;</p>
<p>1) Create a WordPress “<strong>Page</strong>” (not &#8216;post&#8217;) with the text <strong>%%LOGIN_FORM%%</strong> in the body of the page, and a title of say, <strong>Login</strong>, and save the new page. If you used the text &#8220;Login&#8221; for the title, then the actual link to this page would be <strong>YourSite.com/blog/login</strong></p>
<p>2) This page now shows up as &#8220;Login&#8221; along with the rest of your &#8220;pages&#8221; on your blog.</p>
<p>3) Go to DAP Admin &gt; Config &gt; Advanced (drop down). Scroll down to the field that says:</p>
<blockquote><p><strong>Location of your login page (eg., if using WordPress). Should start with a forward slash (`/`)</strong></p></blockquote>
<p>In the text box, enter the link to the login page from Step 1, minus the domain name. So, it would look like:</p>
<blockquote><p><strong>/blog/login</strong></p></blockquote>
<p>That&#8217;s it!</p>
<p>When someone clicks on the &#8220;Login&#8221; link, or tries to access a post that they are not authorized to, the user is redirected to the login page.</p>
<p>Related: <a href="http://www.digitalaccesspass.com/doc/logout-link/">Where is the Logout Link?</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.digitalaccesspass.com/doc/creating-a-login-page-within-wordpress/feed/</wfw:commentRss>
		<slash:comments>18</slash:comments>
		</item>
		<item>
		<title>Using Sneak-Peek For Blog Posts</title>
		<link>http://www.digitalaccesspass.com/doc/using-sneak-peek-for-blog-posts/</link>
		<comments>http://www.digitalaccesspass.com/doc/using-sneak-peek-for-blog-posts/#comments</comments>
		<pubDate>Sun, 22 Feb 2009 23:15:34 +0000</pubDate>
		<dc:creator>Ravi Jayagopal</dc:creator>
				<category><![CDATA[Access Control]]></category>
		<category><![CDATA[Config]]></category>
		<category><![CDATA[Customization]]></category>
		<category><![CDATA[Protection FAQ]]></category>
		<category><![CDATA[Setup]]></category>
		<category><![CDATA[WordPress]]></category>
		<category><![CDATA[WordPress FAQ]]></category>
		<category><![CDATA[WordPress Plugins]]></category>

		<guid isPermaLink="false">http://www.digitalaccesspass.com/doc/?p=29</guid>
		<description><![CDATA[For Advanced Users Only
That means, if you read this post and don&#8217;t understand a word, then this is NOT for you.
For this to work, you must have already installed DAP WP LiveLinks.
Now, when someone comes to your wordpress blog, assuming you have already activated DAP LiveLinks, then none of the posts you have protected will [...]]]></description>
			<content:encoded><![CDATA[<p><strong>For Advanced Users Only</strong></p>
<p>That means, if you read this post and don&#8217;t understand a word, then this is NOT for you.</p>
<p>For this to work, you must have already installed DAP WP LiveLinks.</p>
<p>Now, when someone comes to your wordpress blog, assuming you have already activated DAP LiveLinks, then none of the posts you have protected will even show up on the home page, or will show up if someone tries to visit them directly (say, from a bookmark or link in an email). Which means, as far as your visitor is concerned, those posts don&#8217;t even exist in your blog.</p>
<p>Now as powerful as this plugin is, from an SEO perspective, if your visitor (who is not a member, and one who is not logged in) can&#8217;t even see the post, then neither can Google. This means, if you do a blog-and-ping, when Google arrives at the permalink of your new post, because the post is protected, DAP will redirect Google to your login page. This means, you don&#8217; get the benefit of SEO for your new post.</p>
<p>Also, from a &#8220;Curiosity&#8221; standpoint, if you protect all of the posts, then your visitor will only see a handful of non-protected blog posts.</p>
<p>So, giving them a &#8220;sneak-peek&#8221; of the post your home page as well as on the permalink, is a great way to get them excited about your content.</p>
<p><strong>How to turn on Sneak-Peek</strong></p>
<p>Go to DAP Admin &gt; Config &gt; WordPress Sneak-Peek</p>
<p>It is set to &#8220;N&#8221; (no) by default. Change this to &#8220;Y&#8221; and click on the &#8220;Update&#8221; button to save the change.</p>
<p>And then when they click on the &#8220;more&#8221; button to read the rest of the post, the full post is protected anyway, and they are presented with a login screen.</p>
<p>WARNING: VERY IMPORTANT IF YOU TURN ON SNEAK-PEEK</p>
<p>As soon as you turn on Sneak-Peek, DAP will show all content from your blog posts, but only up to the &#8220;More&#8221; tag. This means, if you don&#8217;t have a &#8220;More&#8221; tag in any of your content, then all of your blog posts will show to all users, regardless of whether they have access or not.</p>
<p>So, the most important thing here is this:</p>
<p><strong>SNEAK-PEEK and MORE are INSEPARABLE.</strong></p>
<p>If you do sneak-peek, you MUST include a &#8220;More&#8221; tag.</p>
<p>So when you create a WordPress blog post, split the post into two parts using the &#8220;More&#8221; tag. This creates a &#8220;public preview&#8221; portion of the actual post, that shows up on your blog&#8217;s home page and in the permalink when that post is displayed. To read the rest of the post, your visitor has to click on the &#8220;More&#8221; link, and that&#8217;s when depending on whether the user has access, the rest of the post will be displayed.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.digitalaccesspass.com/doc/using-sneak-peek-for-blog-posts/feed/</wfw:commentRss>
		<slash:comments>11</slash:comments>
		</item>
		<item>
		<title>DAP WP LiveLinks Plugin</title>
		<link>http://www.digitalaccesspass.com/doc/dap-wp-livelinks-plugin/</link>
		<comments>http://www.digitalaccesspass.com/doc/dap-wp-livelinks-plugin/#comments</comments>
		<pubDate>Sun, 22 Feb 2009 22:56:55 +0000</pubDate>
		<dc:creator>Ravi Jayagopal</dc:creator>
				<category><![CDATA[Access Control]]></category>
		<category><![CDATA[Personalization]]></category>
		<category><![CDATA[WordPress Plugins]]></category>

		<guid isPermaLink="false">http://www.digitalaccesspass.com/doc/?p=28</guid>
		<description><![CDATA[Once you install this plugin, when someone visits your blog, they will ONLY see posts that they are “eligible” to view. This applies to your blog’s main page as well.
So, if a casual visitor arrives at your blog, they only see titles and their summaries for posts that have NOT been protected (not added to [...]]]></description>
			<content:encoded><![CDATA[<p><strong></strong>Once you install this plugin, when someone visits your blog, they will ONLY see posts that they are “eligible” to view. This applies to your blog’s main page as well.</p>
<p>So, if a casual visitor arrives at your blog, they only see titles and their summaries for posts that have NOT been protected (not added to DAP at all).</p>
<p>For instance, if you have 100 posts, and have protected 95 of them, then on your blog’s home page, this visitor will see only 5 blog posts &#8211; titles and summaries &#8211; in TOTAL.</p>
<p>They won’t even see the titles or bodies of the protected posts. And if they somehow get the link to it (from someone else, by email, say) and try to visit it, then the existing DAP protection kicks in, and they’re asked to login first to determine if they have access to that post &#8220;as of now”.</p>
<p>But once this same visitor logs in, all blog posts that were HIDDEN earlier MAGICALLY re-appear <img class="wp-smiley" src="../../blog/wp-includes/images/smilies/icon_wink.gif" alt=";-)" /> And they see all posts that they are CURRENTLY eligible to access (this excludes posts to which access already expired, and posts to which they don’t have access YET &#8211; i.e., future availability).</p>
<p>If you want a certain portion of even your protected posts to always show up, even if the user is not eligible to see the post, see DAP &#8220;Sneak-Peek&#8221;.</p>
<p>This plugin lets you do two other things:</p>
<p>1) You can PERSONALIZE blog post titles and content with MERGE variables.</p>
<p>So, if you create a blog post with the title “<strong>Welcome %%FIRST_NAME%%</strong>“, then when your member logs in, they will see “<strong>Welcome John</strong>“.</p>
<p>Available merge variables;</p>
<p><strong>%%FIRST_NAME%%</strong> -  Gets replaced with their first name</p>
<p><strong>%%EMAIL%%  &#8211; </strong>Gets replaced with their email</p>
<p><strong>%%MEMBER_HOME_PAGE%%</strong> -  Gets replaced with the &#8216;login&#8217; page</p>
<p>2) You can also put the <a href="http://www.digitalaccesspass.com/doc/creating-a-login-page-within-wordpress/">Login Form on any WP “Page”</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.digitalaccesspass.com/doc/dap-wp-livelinks-plugin/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Personalization For Your Blog Posts</title>
		<link>http://www.digitalaccesspass.com/doc/personalization-for-blog-posts/</link>
		<comments>http://www.digitalaccesspass.com/doc/personalization-for-blog-posts/#comments</comments>
		<pubDate>Fri, 22 Feb 2008 23:43:05 +0000</pubDate>
		<dc:creator>Ravi Jayagopal</dc:creator>
				<category><![CDATA[Access Control]]></category>
		<category><![CDATA[Customization]]></category>
		<category><![CDATA[Personalization]]></category>
		<category><![CDATA[Setup]]></category>
		<category><![CDATA[WordPress]]></category>
		<category><![CDATA[WordPress Plugins]]></category>

		<guid isPermaLink="false">http://www.digitalaccesspass.com/doc/?p=30</guid>
		<description><![CDATA[1) Personalize post Titles and Content with MERGE variables:
%%FIRST_NAME%% -  Gets replaced with their first name
%%EMAIL%%  &#8211; Gets replaced with their email
%%MEMBER_HOME_PAGE%% -  Gets replaced with the &#8216;login&#8217; page
So if you create a blog post with the title “Welcome %%FIRST_NAME%%“, then when your member views that post after they&#8217;ve logged in, they will see “Welcome [...]]]></description>
			<content:encoded><![CDATA[<p>1) <strong>Personalize post Titles and Content with MERGE variables</strong>:</p>
<p><strong>%%FIRST_NAME%%</strong> -  Gets replaced with their first name<br />
<strong>%%EMAIL%%  &#8211; </strong>Gets replaced with their email<strong><br />
%%MEMBER_HOME_PAGE%%</strong> -  Gets replaced with the &#8216;login&#8217; page</p>
<p>So if you create a blog post with the title “<strong>Welcome %%FIRST_NAME%%</strong>“, then when your member views that post after they&#8217;ve logged in, they will see “<strong>Welcome John</strong>“.</p>
<p>2) <strong>Personalize the Login Form:</strong></p>
<p>You can put the <a href="http://www.digitalaccesspass.com/doc/creating-a-login-page-within-wordpress/">Login Form on any WP “Page”</a>.</p>
<p>3) <strong>Personalize Member and Affiliate Information:</strong></p>
<p>Put <a href="http://www.digitalaccesspass.com/doc/creating-member-affiliate-sections-within-wordpress/">Member &amp; Affiliate Info on any WP Page</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.digitalaccesspass.com/doc/personalization-for-blog-posts/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>
