1-Click Upsells, Downsells and OTO’s are now extremely simple to implement using the new “Upsell Tree” plugin for DAP.

And this plugin works with Paypal Website Payments Pro!

What you need before you can use this plugin

1. You need a Paypal Website Payments Pro merchant account with Recurring Billing enabled.
2. You must have SSL (secure server) enabled on your web site. Ask your web host to enable SSL for your site.
3. You must have a working version of DAP 3.6+.

Installation & Setup of UpsellTree

1. You need at least DAP v3.6 for this. So login to your DAP account and download the latest version of DAP and the LiveLinks.
2. Follow standard procedure for installing DAP (OR) upgrading your DAP & LiveLinks versions. Nothing different there.
3. Purchase the UpsellTree plugin, login to your DAP account and download the plugin zip file, PaypalUpsellTree.zip .
4. Unzip PaypalUpsellTree.zip to your desktop. It will unzip the files to a new folder on your desktop, called “PaypalUpsellTree”.
5. Upload all the files inside, directly to your “dap” folder on your web site. DO NOT upload the folder itself.
6. Log in to your Paypal account and retrieve the following 3 pieces of information:
   * Paypal API Username
   * Paypal API Password
   * Paypal API Signature
7. Now log in to your DAP Dashboard and go to “Config > Payment Processing“.
8. Enter the Paypal API Username, Paypal API Password, and Paypal API Signature that you noted down earlier (Step #9 above) into the respective fields, and click  “Update” next to the fields to save the changes.
9. This step applies to you only if you are already using 1ShoppingCart with DAP (if not, skip to next step):
   Be sure to disable the “Email Order” cron job from your web hosting control panel (“Cron Jobs” screen), because you don’t want your orders to be double-processed.
10. Go to the “Products” page. You will now see a few new fields (some because of of DAP 3.5, some because of the new plugin).
    
    A) Product Price: For a 1-time purchase product, this is the product’s purchase price. For a recurring product, this is the “recurring” price (what the customer gets charged month after month).
    B) Trial Amount: This is only if there’s a trial amount. If no trial, leave this empty.
    C) Recurring Count: How long is your subscription? If you said “Forever”, then enter the number 9999 here. If it ends after 6 months, then enter 6 here.
11. Set these fields to valid values.
12. NOTE: The DAP Authorize.net allows 1 trial. So in the recurring cycle fields, make sure “Payment/Trial Period #2″ and “Payment/Trial Period #3″ are both the same (set to same number of days: like 30). Example below shows the setting for a “7 day” trial period, followed by recurring payments every “30 days”.
    
13. If you are not offering a trial, then just set the Trial Amount to $0.00. But if you really wanted to offer a FREE TRIAL, then you must set the Trial Amount to at least $0.01 (1 penny).
14. Once you’ve saved the product, you can now click on any of the two new “Generate… Button Code” links that are located right below the product list combo box. Image below shows the Authnet links. Similar buttons will show up for Paypal too.
    
15. “Generate Paypal Buy Button” link:
    This generates the buy button HTML code for your product, which you can then directly paste into your sales page. When you click on this link, you will get a pop-up that shows the actual HTML code for your button. The price, trial price, and recurring options are all taken from your Product settings. So make sure you have saved your Product changes before you click on this link.
    
16. Here’s what the HTML code looks like:
    <form name="generate_paypal" method="post" action="https://www.contentresponder.com/dap/buy.php">
<input type="hidden" name="item_name" value="Example Subscription Product"/>
<input type="hidden" name="description" value="This is a dummy Subscription Product with a monthly subscription - payments every 30 days." />
<input type="hidden" name="amount" value="1.00" />
<input type="hidden" name="trial_amount" value="0.01" />
<input type="hidden" name="total_occurrences" value="9999" />
<input type="hidden" name="is_recurring" value="Y" />
<input type="hidden" name="recurring_cycle_1" value="30" />
<input type="hidden" name="recurring_cycle_2" value="30" />
<input type="hidden" name="recurring_cycle_3" value="30" />
<input type="hidden" name="payment_succ_page" value="https://www.contentresponder.com/dap/continue.php?url=/dap/upsell1.html" />
<input type="hidden" name="payment_gateway" value="authnet" />
<input type="hidden" name="is_submitted" value="Y" />
<input type="submit" value="Buy Now" />
</form>
17. If you’re doing upsells, the only thing you need to do is, look for the “payment_succ_page” field in the above form. By default it is pointing to:
    https://www.contentresponder.com/dap/continue.php?url=/dap/upsell1.html
18. Modify the “upsell1.html” file within your dap folder, to make your 1-Click Upsell offer. Or if you don’t wish to use 1-Click upsells, you can make just about any kind of upsell offer on that page. The upsell1.html that comes with the plugin has a sample upsell page already created for you, just so you get an idea of what that will look like.
19. On the upsell page, if you want to upsell say, Product B, then make sure you set up “Product B” ahead of time in DAP, and set up the price and recurring options. Then for upsell products only, click on the “Generate Authnet 1-Click Upsell” link to generate the 1-Click Upsell Buy button code, as the upsell buy button is slightly different than the ‘regular’ buy button code. Now take the upsell buy button code like you did before, and paste it in upsell1.html. That’s it.
20. You can repeat this process for unlimited upsells, downsells and one-time offers. No limits.

That’s it.

While it looks like a LOT of steps, that is only because we have to explain the steps in detail so they are clear. In reality, it is very simple to set up, and starting from scratch, if you have DAP & SSL already installed, it shouldn’t take you more than 1/2 hour to set up your 1-Click Upsells/Downsells/OTO’s. And if you’re not using Upsells/Downsells, then it can be done even faster.

If you have any further questions, feel free to open a support ticket, and we will assist you in getting this going.

Here are the merge-tags that you can use in your WP posts, and what they mean.

%%MSG%%

1) Create a WP “page” with the slug “error”, and it can be accessed at http://YourSite.com/error/

2) In the body of the page, put the text %%MSG%% – followed by whatever copy you want.

3) Enter the URL from Step #1 on your “Products” page, in the field “Error Page URL”

4) Logout of DAP, and log back in for the changes to take effect.

Impact: When someone tries to visit a link that has expired, or a link that they don’t have access to, they will be redirected to the above URL, and the system error message will be shown where you put in the merge code %%MSG%%.

%%SALES_PAGE_URL%%

This text in your blog post/page content, will be replaced by the “Sales Page URL” field from the Products page.

%%AFFDETAILS%%

This will be replaced by the entire Affiliate section from the default home page at YourSite.com/dap/

%%USERPROFILE%%

This will be replaced by the user profile from the default home page at YourSite.com/dap/

%%USERLINKS%%

This will be replaced by the user links section (the list of what products and what links user currently has access to) from the default home page at YourSite.com/dap/

%%FIRST_NAME%%

This will be replaced by the first-name of the user.

%%EMAIL%%

This will be replaced by the email id of the user.

%%MEMBER_HOME_PAGE%%

This will be replaced by whatever is in “Config > Advanced > URL of your User-Profile page”

%%AFF_LINK%%

This will be replaced by the raw affiliate link of the member. If you want it to show up as a link in your blog post, use it like this:

<a href=”%%AFF_LINK%%”>%%AFF_LINK%%</a>

DAP has a Login/Logout Widget that you can use in any widget-ready theme.

Log in as WP admin, and look under “Appearance > Widgets”.

You’ll see the widget. Drag this widget on to any customizable part of your theme.

The widget puts the DAP login form right on your sidebar.

When a user is not logged in, they will see the login form.

When they are logged in, they just see a “Logout” button.

(1) When Activating LiveLinks

If you are seeing an error that looks like this when you try to activate LiveLinks…

Fatal error: Cannot redeclare dap_filter_posts() (previously declared in /home/birdtric/public_html/wp-content/plugins/DAP-WP-LiveLinks/DAP-WP-LiveLinks.php:11) in /home/birdtric/public_html/wp-content/plugins/DAP-WP-LiveLinks/DAP-WP-LiveLinks.php on line 11

Solution A) This could be because you have incorrectly named the DAP or Livelinks folders.

Remember, the dap folder must always be named dap (all lower case – and not, say, dap_v3.0). And the livelinks folder must be named DAP-WP-LiveLinks .

Solution B) It is possible that your web site does not meet the minimum requirements to run DAP .

If you open a ticket and give us your FTP info and your WordPress Admin login info, we can confirm this to you right away.

— *** —

If you are seeing an error that looks like this when you try to activate LiveLinks…

Oops! Could not create the config file (dap-config.php). Please make the ‘dap’ folder writable by doing CHMOD 755 (and if that doesn’t work, then try CHMOD 777.)
Installation failed. Please de-activate LiveLinks and re-activate it when you’ve fixed the issue. (106)

* CHMOD just the dap directory to 777.
* Then de-activate and activate the LiveLinks plugin.
* This time around, it should be able create the dap-config.php file within the dap directory. You should see the successful installation message.
* CHMOD just the dap directory back to 755.

If that doesn’t work, then open a ticket with the FTP info and WP admin info.

————————————————————

(2) Session Error

If you see an error that looks like this…

Fatal error: Dap_Session::isLoggedIn() [dap-session.isloggedin]: The script tried to execute a method or access a property of an incomplete object. Please ensure that the class definition “Dap_Session” of the object you are trying to operate on was loaded _before_ unserialize() gets called or provide a __autoload() function to load the class definition in /home/site/public_html/dap/inc/classes/Dap_Session.class.php on line 41

This is basically caused by someone else’s 3rd-party WordPress plugin that is wiping out the “session” data (or user data stored in memory) which DAP relies on to store the user information. So there are two things you can try…

1. See if you have a plugin by name “WordPress Automattic Upgrade” in your wordpress plugins page.This has created many issues for so many other plugins too, including LiveLinks. Just de-activate this plugin, and your error should go away. Also, if you are using WordPress version 2.7.1, you don’t really need this plugin any more – the automatic upgrade feature has been built right into this version.
2. See if you have a plugin for doing “Captcha” – this is where to prevent bots from spamming your comments, your visitor is presented with some kind of an image to verify that they are human. Try with that de-activated.
3. If none of the above worked, or if you don’t have any of the above plugins active and you’re still seeing the error, then just try de-activating all other plugins temporarily (except LiveLinks, of course), and turn them back on one-by-one.

Refresh your blog page every time you activate a plugin. That way, you will know which is the plugin that is causing the error.

If that still doesn’t help, just open a support ticket and we’ll take care of it.

————————————————————

(3) PDO Error

You see an error like this:

Fatal error: Class ‘PDO’ not found in /home1/knowlee3/public_html/buildamagneticnetwork/dap/inc/classes/Dap_Connection.class.php on line 19

If DAP had been working fine on your web site, and you all of a sudden see this error, then your host quietly pulled the rug from under your feet . This appears because they either deliberately or mistakenly disabled the “PDO” library, which is a must-have requirement for DAP to run.

So check with your host and ask them “if they disabled PHP/PDO for MySQL on your server recently”.

————————————————————

(4) Memory Allocation

You see an error like this:

Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 16 bytes) in /home/yoursite.com/public_html/dap/inc/classes/Dap_Connection.class.php on line 19

If this happens just once, then just ignore it.

But if it occurs more than once, then it could be because:

a) You recently made some changes to your DAP files or web site files, and overwrote/updated your dap-config.php file with the wrong database information. Even though it shows up like a memory issue, in reality it could be because DAP is unable to connect to the database because of incorrect information in the dap config file.

b) Your server legitimately has a low memory limit set by your host, and your host needs to increase the memory allocated to PHP/PDO. Open a ticket with your web host to do this.

————————————————————

(5) Simple-Pie & Memory Allocation

You see an error like this:

Fatal error: Allowed memory size of 37423432 bytes exhausted (tried to allocate 371520 bytes) in /…/public_html/~username/wp-includes/class-simplepie.php

Open the file wp-config.php (which is in your blog’s main folder)

Add this line at the top…

define('WP_MEMORY_LIMIT', '64M');

That should take care of the error.