<?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: Product Chaining</title>
	<atom:link href="http://www.digitalaccesspass.com/blog/2010/04/product-chaining/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.digitalaccesspass.com/blog/2010/04/product-chaining/</link>
	<description>Membership Script For WordPress</description>
	<lastBuildDate>Fri, 03 Feb 2012 20:14:20 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Veena Prashanth</title>
		<link>http://www.digitalaccesspass.com/blog/2010/04/product-chaining/comment-page-1/#comment-526</link>
		<dc:creator>Veena Prashanth</dc:creator>
		<pubDate>Tue, 04 May 2010 18:57:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.digitalaccesspass.com/blog/?p=298#comment-526</guid>
		<description>Ryan,
We are considering adding a &#039;product chaining effective date&#039; that will allow you to specify exactly when you want the specific product chaining rule to take effect. By default, it will be set to current date.

If it&#039;s a paid product, then the subscription payment notification will always come in referencing the old product name. It cannot be automatically transferred or Applied-To the new product every year.</description>
		<content:encoded><![CDATA[<p>Ryan,<br />
We are considering adding a &#8216;product chaining effective date&#8217; that will allow you to specify exactly when you want the specific product chaining rule to take effect. By default, it will be set to current date.</p>
<p>If it&#8217;s a paid product, then the subscription payment notification will always come in referencing the old product name. It cannot be automatically transferred or Applied-To the new product every year.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan Bruss</title>
		<link>http://www.digitalaccesspass.com/blog/2010/04/product-chaining/comment-page-1/#comment-517</link>
		<dc:creator>Ryan Bruss</dc:creator>
		<pubDate>Tue, 04 May 2010 03:48:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.digitalaccesspass.com/blog/?p=298#comment-517</guid>
		<description>Is it possible w/ this to create a product that is a 1 year membership (Product: Year 1)...the customer is dripped content for 1 year...and then when this period is over they are automatically signed-up for another 1 year membership (Product: Year 2)?  I have been hoping for a feature like this so instead of customers signing-up for a limitless membership they sign up for an automatically renewed 1 year package of lessons.  New customers can then choose what year to start at and I have more control over the lessons and a defined end to the membership (whatever year I stop creating lessons).</description>
		<content:encoded><![CDATA[<p>Is it possible w/ this to create a product that is a 1 year membership (Product: Year 1)&#8230;the customer is dripped content for 1 year&#8230;and then when this period is over they are automatically signed-up for another 1 year membership (Product: Year 2)?  I have been hoping for a feature like this so instead of customers signing-up for a limitless membership they sign up for an automatically renewed 1 year package of lessons.  New customers can then choose what year to start at and I have more control over the lessons and a defined end to the membership (whatever year I stop creating lessons).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Veena Prashanth</title>
		<link>http://www.digitalaccesspass.com/blog/2010/04/product-chaining/comment-page-1/#comment-514</link>
		<dc:creator>Veena Prashanth</dc:creator>
		<pubDate>Tue, 04 May 2010 02:28:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.digitalaccesspass.com/blog/?p=298#comment-514</guid>
		<description>Right. It&#039;s one level deep. 

Otherwise it can get very complex and hard to troubleshoot.</description>
		<content:encoded><![CDATA[<p>Right. It&#8217;s one level deep. </p>
<p>Otherwise it can get very complex and hard to troubleshoot.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: LisaSEO</title>
		<link>http://www.digitalaccesspass.com/blog/2010/04/product-chaining/comment-page-1/#comment-509</link>
		<dc:creator>LisaSEO</dc:creator>
		<pubDate>Mon, 03 May 2010 22:01:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.digitalaccesspass.com/blog/?p=298#comment-509</guid>
		<description>How many levels of product chaining? looks like one level deep, right?</description>
		<content:encoded><![CDATA[<p>How many levels of product chaining? looks like one level deep, right?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Coming Soon: DAP v3.8 &#38; LL v1.3 &#8212; The DAP Blog</title>
		<link>http://www.digitalaccesspass.com/blog/2010/04/product-chaining/comment-page-1/#comment-498</link>
		<dc:creator>Coming Soon: DAP v3.8 &#38; LL v1.3 &#8212; The DAP Blog</dc:creator>
		<pubDate>Mon, 03 May 2010 15:52:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.digitalaccesspass.com/blog/?p=298#comment-498</guid>
		<description>[...] [NEW] Product Chaining [...]</description>
		<content:encoded><![CDATA[<p>[...] [NEW] Product Chaining [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ravi Jayagopal</title>
		<link>http://www.digitalaccesspass.com/blog/2010/04/product-chaining/comment-page-1/#comment-497</link>
		<dc:creator>Ravi Jayagopal</dc:creator>
		<pubDate>Mon, 03 May 2010 15:18:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.digitalaccesspass.com/blog/?p=298#comment-497</guid>
		<description>FYI: Update Product Chaining screenshot.

- Ravi Jayagopal</description>
		<content:encoded><![CDATA[<p>FYI: Update Product Chaining screenshot.</p>
<p>- Ravi Jayagopal</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lee Jackson</title>
		<link>http://www.digitalaccesspass.com/blog/2010/04/product-chaining/comment-page-1/#comment-495</link>
		<dc:creator>Lee Jackson</dc:creator>
		<pubDate>Tue, 27 Apr 2010 07:49:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.digitalaccesspass.com/blog/?p=298#comment-495</guid>
		<description>I love the concept of add and remove. I for one hate it when after I purchase a product and  still receive promotional material for the same product as if I never made the purchase. 

This certainly will be great for my customers. Thanks for the great upgrade keep up the great work.</description>
		<content:encoded><![CDATA[<p>I love the concept of add and remove. I for one hate it when after I purchase a product and  still receive promotional material for the same product as if I never made the purchase. </p>
<p>This certainly will be great for my customers. Thanks for the great upgrade keep up the great work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Veena Prashanth</title>
		<link>http://www.digitalaccesspass.com/blog/2010/04/product-chaining/comment-page-1/#comment-487</link>
		<dc:creator>Veena Prashanth</dc:creator>
		<pubDate>Mon, 26 Apr 2010 02:23:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.digitalaccesspass.com/blog/?p=298#comment-487</guid>
		<description>Fern,
It&#039;s a good concept but not something we are supporting because this will result in a scenario where free customers that upgrade after say 4 months have access to ALL the content on day 1 of their upgrade while other paid users would have paid for 4 months to have access to the same content. It will not be a fair deal for the paid customers who have been paying monthly for all those months.

The access start of the chained products will be the date they upgrade and will not (and ideally should not) match the access start date of the product they currently have.</description>
		<content:encoded><![CDATA[<p>Fern,<br />
It&#8217;s a good concept but not something we are supporting because this will result in a scenario where free customers that upgrade after say 4 months have access to ALL the content on day 1 of their upgrade while other paid users would have paid for 4 months to have access to the same content. It will not be a fair deal for the paid customers who have been paying monthly for all those months.</p>
<p>The access start of the chained products will be the date they upgrade and will not (and ideally should not) match the access start date of the product they currently have.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fern</title>
		<link>http://www.digitalaccesspass.com/blog/2010/04/product-chaining/comment-page-1/#comment-486</link>
		<dc:creator>Fern</dc:creator>
		<pubDate>Mon, 26 Apr 2010 01:45:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.digitalaccesspass.com/blog/?p=298#comment-486</guid>
		<description>Brilliant! So the scenerio below will be true:

A client signs up for a free ad-supported membership version on my site labeled Product A, in the back ground simultaneously they are registered for Product B (paid ad-free version of Product A), but does not have access to it yet. 

Product B is only keeping pace with Product A so if a client is 3 weeks into A then they&#039;ll be 3 weeks into B. The client doesn&#039;t receive any content access or email drips from B. 

When a client decides to upgrade to Product B they&#039;ll be in the same chronological position in their membership only with the ads removed making the upgrade seamless and invisible to the client. 

If the client downgrades it reverts them back to Product A at the same position they were in right before the cancel.</description>
		<content:encoded><![CDATA[<p>Brilliant! So the scenerio below will be true:</p>
<p>A client signs up for a free ad-supported membership version on my site labeled Product A, in the back ground simultaneously they are registered for Product B (paid ad-free version of Product A), but does not have access to it yet. </p>
<p>Product B is only keeping pace with Product A so if a client is 3 weeks into A then they&#8217;ll be 3 weeks into B. The client doesn&#8217;t receive any content access or email drips from B. </p>
<p>When a client decides to upgrade to Product B they&#8217;ll be in the same chronological position in their membership only with the ads removed making the upgrade seamless and invisible to the client. </p>
<p>If the client downgrades it reverts them back to Product A at the same position they were in right before the cancel.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tweets that mention Product Chaining — The DAP Blog -- Topsy.com</title>
		<link>http://www.digitalaccesspass.com/blog/2010/04/product-chaining/comment-page-1/#comment-485</link>
		<dc:creator>Tweets that mention Product Chaining — The DAP Blog -- Topsy.com</dc:creator>
		<pubDate>Mon, 26 Apr 2010 01:19:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.digitalaccesspass.com/blog/?p=298#comment-485</guid>
		<description>[...] This post was mentioned on Twitter by Ravi Jayagopal, Ravi Jayagopal. Ravi Jayagopal said: Check out DAP&#039;s newest feature, &quot;Product Chaining&quot;: http://www.digitalaccesspass.com/blog/2010/04/product-chaining/ [...]</description>
		<content:encoded><![CDATA[<p>[...] This post was mentioned on Twitter by Ravi Jayagopal, Ravi Jayagopal. Ravi Jayagopal said: Check out DAP&#39;s newest feature, &quot;Product Chaining&quot;: <a href="http://www.digitalaccesspass.com/blog/2010/04/product-chaining/" rel="nofollow">http://www.digitalaccesspass.com/blog/2010/04/product-chaining/</a> [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

