DAP Admin

Author Archives: DAP Admin

36

Integrating DAP with Paypal Standard

This doc applies to Paypal Standard only.

(Click here for integration with Paypal Website Payments Pro)

You do not have to log in to your Paypal account to generate your buy buttons. You can do it from within the DAP Admin Dashboard.

1) Enabling Instant Payment Notification (IPN) within your Paypal account.

a) Log in to your Paypal account and click on the “Profile” link in the menu, then on the next page, click “My selling tools.”
b) Under “Getting paid and managing risk” section, click “Update” beside “Instant payment notifications”
c) If IPN is already enabled, and you already have a URL in that field, then skip ahead to Step 2.
Else, if IPN is not already enabled, then click on “Choose IPN Settings”

d) On the next screen, in the Notification URL field, enter…
http://YourSite.com/dap/dap-paypal.php
Don’t forget to replace “YourSite.com” with your actual web site’s domain name.

e) Make sure “Receive IPN Messages” is selected.

f) Click on “Save”.

2) Enable “Auto-Return” and “Payment Data Transfer”

  • Log in to your Paypal account.
  • Go to Profile.
  • Click on Website Payment Preferences
  • Turn Auto Return to On (see image below)
  • Set Return URL to http://YourSite.com/dap/dap-thankyou.php
  • Scroll down further to the Payment Data Transfer (optional) section
  • Set Payment Data Transfer to On
  • Scroll all the way to the bottom of the page, and then Save the changes.
  • Now come back to this same page just like you did before (Profile > Website Payment Preferences)
  • This time, simply scroll down to the Payment Data Transfer (optional) section
  • Now you will see a long, ugly string of text next to the Identity Token field (see image below). Copy that string.
  • Go back to DAP Dashboard > Setup > Config > Payment Processing > Paypal Identity Token field, and enter this string there, and save it.

 

3) Config settings

Go to “Setup > Config“.

Click on the Paypal link in the sub-menu at the top.

The current page will then skip to the “Payment Processing: Paypal” section about half-way down the page.

Fill out items 1 through 5 only.

(items 7-10 are required only if you’re using Paypal Website Payments Pro, or doing Upsells with Paypal Standard)

4) Generate Buy Button from within DAP

On the main DAP Admin menu, go to Payment Processing > Generate Buy Buttons page, then switch to Paypal Standard tab

Choose product for which you wish to generate the buy button, and then click on “Generate Button Code” button.

5) Publish generated buy-button code on your Sales page.

That’s it!

Sales Flow

Here’s how the flow works now:

  • Prospect clicks on buy-button your sales page and is taken to a Paypal checkout page at Paypal.com
  • They purchase your product and complete the payment
  • They are initially redirected to the “Auto Return” url from Step 2 above
  • DAP captures customer email, name, product name, etc
  • DAP creates member account for buyer on your system, and gives them access to the product, will send out the Welcome-Email from the product page, etc
  • It auto-logs them in to your membership site – no need for member to wait for Welcome email just to get their login information (that email is sent anyway, and will be waiting for them in their inbox)
  • DAP now needs to know where to redirect the user to.
    a) If Product-level Logged-In URL is set in DAP for this Product that they just purchased, then it redirects them to that URL
    b) If no Product-level Logged-In URL is set, OR if the buyer has access to more than 1 product (if they had previously purchased another one of your products, for example), then it uses the Global “Logged-In URL” setting from: Setup > Config > Advanced > URL to which user is redirected to right after login

2) DAP Generated Buttons For Paypal

With DAP 4.0, we have added support for DAP generated buttons for Paypal.  You no longer have to generate buttons within Paypal.

24

Paypal Integration Summary

DAP supports 3 different types of Paypal Integration.

1) Paypal Hosted Buttons
2) DAP Generated Buttons For Paypal
3) DAP Shopping Cart with Upsells

Let’s get into more details about each one of them.

[s3mv]DAP-Paypal-Integration-Overview.mp4,640,350,false,false[/s3mv]

1) Paypal Hosted Buttons

You generate the button within your Paypal account.

Click Here to find instructions to integrate DAP and Paypal Hosted Buttons.

If the integration is not working, Click Here to find troubleshooting instructions.

Note: you only need to set the following config items for Paypal hosted buttons.

a) If you want to use Paypal Sandbox for testing, then set the following to “Y”.
DAP Setup -> Config -> Paypal -> Use Paypal Sandbox: For initial testing only

If you want to connect to your Paypal live account, then set it to “No”.

b) If your site has trouble connecting to Paypal via CURL and you see this error in DAP orders page => Check Product and Price(Reprocessible), then update the config below to FOPEN.

DAP Setup -> Config -> Paypal -> 4) Paypal Communication Protocol: How DAP connects to and communicates with Paypal on the back-end.

That’s it.

The following config items are NOT needed if you use the Paypal hosted buttons.

Paypal API Username – Only needed if you use the DAP upsell tree plugins for Paypal Payments Pro or Paypal Standard.
Paypal API Password – Only needed if you use the DAP upsell tree plugins for Paypal Payments Pro or Paypal Standard.
Paypal API Signature – Only needed if you use the DAP upsell tree plugins for Paypal Payments Pro or Paypal Standard.
Paypal API Endpoint – Only needed if you use the DAP upsell tree plugins for Paypal Payments Pro or Paypal Standard.

Paypal Business Email ID – Only needed if you use the DAP generated button for Paypal (DAP Payments/Coupons -> Generate paypal button)

Merchant Payment Gateway API Login ID: Only needed if you use e-junkie or the DAP upsell tree plugin for Authorize.net
Merchant Payment Gateway Transaction Key: Only needed if you use e-junkie or the DAP upsell tree plugin for Authorize.net

The following fields in the DAP Products page ONLY need to be set if you use DAP upsell tree plugin or the DAP generated button for Paypal.

Recurring Count, Trial Amount and Product Price

If you are using regular paypal button, you can leave these empty. Even if these are not-empty, DAP will not use it for regular paypal hosted buttons.

2) DAP Generated Buttons For Paypal

With DAP 4.0, we have added support for DAP generated buttons for Paypal. You no longer have to generate buttons within Paypal.

You can generate the button for Paypal from within your DAP Admin Panel -> Payment Processing -> Generate Paypal Button page.



Click Here to find instructions to integrate the DAP generated button with Paypal.

3) DAP Shopping Cart / DAP Upsell Tree Plugins

1) Paypal Standard Upsell Tree Plugin
2) Paypal Payments Pro Upsell Tree Plugin / DAP shopping cart

Click Here for details.

2

Protect Entire Blog

If you, for some reason, need to protect your ENTIRE blog from “non-logged in users” – meaning, any part of your blog (menus, sidebars, widgets, etc), including the un-protected pages, should be seen only by someone who is already logged in – be it a free user or a paid user, then here’s how you do it…

  1. Go into your WordPress Admin, click on Appearance > Editor
  2. Make sure your current theme is selected in the drop-down towards the right/top corner.
  3. Click on “Header” (header.php) of your theme.
  4. Enter the following text right towards the very top of that file.

<?php
include_once “./dap/dap-config.php”;

if( !Dap_Session::isLoggedIn() ) {
header(“Location: /dap/login.php”);
exit;
}
?>

The only thing you need to make sure is that you have the path to the dap-config.php correct.

If your blog is in the root, then use the code above as is.

If your blog is in a sub-folder, then replace line in red above, with the line in red below…

include_once “../dap/dap-config.php”;

That’s it!


WARNING

Please remember that if you do this, then you must use the default DAP login page /dap/login.php , and you won’t be able to put the login form within WordPress.

The reason for this, is that the protection code is being applied at the theme level, and the protection will also apply to all WordPress pages and posts – and if you put the DAP login form inside a WP page, then that page will also get protected from everyone, and no one will even be able to get to the login form in order to log in. That makes your site impossible to log in to, which of course makes no sense.

54

DAP Shortcodes

DAP has a feature called “DAP Shortcodes” that allows you to do partial or in-page content protection.

(RELATED: If you are looking for merge tags to place into WordPress posts, then see Merge Tags for WordPress. For email-related merge tags, see Merge Tags for Email).

So if you had a blog post or page with 3 paragraphs of text and a video, you can protect just the video from certain groups of viewers, and leave the text portions open for anyone to read.

And you can…

a) Replace the text that is enclosed by the short codes with an error message.

So entering this in to your page/post’s body…

… then becomes this…

You can fully customize the style and text of the error message.

Or…

b) You can make the private text completely disappear from the page

By adding an additional parameter to the shortcode, you can make the error message completely disappear.

So this…

…is seen like this by the visitor…

No error message at all – like that section of content never even existed, and no errors or warnings shown either.

 

Teaser On Steroids

The DAP Shortcodes may be used to quickly protect content that you don’t necessarily wish to create a DAP Product for.

So if you don’t care about dripping some content, but just wish to protect it from say, non-members, or make it available only to certain “levels”, then you can do it by using the DAP Shortcode, and not have to worry about adding it to any particular level first.

These Shortcodes may or may not be used within content that is already protected as part of a DAP Product. Totally up to you.

Shortcode Summary

This section just lists all of the available shortcodes so you can quickly see everything in one glance. Details about each shortcode is available in the next section below.

Basic DAP Shortcode
[DAP]...private content...[/DAP]

Expanded DAP Shortcode Options
[DAP]...private...[/DAP] [DAP hasAccessTo="1" errMsgTemplate=""]...private...[/DAP] [DAP hasAccessTo="1,2,3" errMsgTemplate="SHORT"]...private...[/DAP] [DAP hasAccessTo="1" errMsgTemplate="SHORT"]...private...[/DAP] [DAP hasAccessTo="1,2,3" errMsgTemplate="LONG"]...private...[/DAP]

Member-Specific Content
[DAP userId="144"]protected content[/DAP]

In-Page Dripping
[DAP startday="1" endday="9999" hasAccessTo="1"]Video 1 Embed Code[/DAP] [DAP startday="2" endday="9999" hasAccessTo="1"]Video 2 Embed Code[/DAP] [DAP startday="3" endday="9999" hasAccessTo="1"]Video 3 Embed Code[/DAP]

If you don’t include endday in your shortcode, then the default value for endday is taken as 9999 – which means forever access.

Hiding Content From Logged-In Members
(a.k.a showing content only to visitors)
[DAP isLoggedIn="N"]....content to show only to NON-members... [/DAP]

Showing Different Content To Visitors -vs- Members
Use both codes as shown below (one following the other):

[DAP isLoggedIn="N"]....sales page content shown only to visitors (and members who have not yet logged in)...[/DAP][DAP isLoggedIn="Y"]...member content that will replace sales content shown only to logged-in members...[/DAP]
publicUntil
[DAP publicUntil="2012-12-31" hasAccessTo="1"]This message will be completely public UNTIL (and including) December 31st, 2012 after which it will be protected as part of product 1[/DAP]

publicAfter
[DAP publicAfter="2012-01-01" hasAccessTo="1"]This message will be completely public AFTER (and including) January 1st, 2012 until which time it will be protected as part of product 1[/DAP]

hasNoAccessTo
[DAP hasAccessTo="2" hasNoAccessTo="1,3" ]This message will appear only to active users of product 2 but only for those who DO NOT also have access to products 1 or 3[/DAP]

startday / endday
[DAP hasAccessTo="2" startday="1" endday="1"]This message will appear to you only to users of Product 2, on Day 1 and no further[/DAP]

startdate / enddate
[DAP hasAccessTo="2" startdate="2012-01-01" enddate="2012-01-31"]This message will appear to you only to users of Product 2, between the dates of Jan 1st, 2012 and Jan 31st, 2012 - and no further[/DAP]
Negative Days
[DAP hasAccessTo="2" startDay="-6" endDay="-3"]Howdy[/DAP]

Error Message From File
[DAP hasAccessTo="2" startday="1" endday="1" errMsgTemplate="file:http://YourSite.com/customMessage.html"]This message will appear to you only today[/DAP]

[DAPUserLinks]

[DAPUserLinks showProductName="Y" showAccessStartDate="Y" showAccessEndDate="Y" showDescription="Y" showLinks="Y" orderOfLinks="NEWESTFIRST" howManyLinks="10000" errMsgTemplate="SHORT" productId="ALL" dateFormat="YYYY-MM-DD" showproductcount="Y"]

orderOfLinks

orderOfLinks can have one of two values…

NEWESTFIRST will drip newly dripped links at the top. So day 7 link will be above day 1 link.

OLDESTFIRST will drip newly dripped links towards the bottom. So day 1 link will be above day 7 link.

showproductcount=”N” will disable the heading “You have access to X products” at the top of the “My Content” section.

So, here’s another version of the DAPUserLinks shortcode:

[DAPUserLinks showProductName="Y" showAccessStartDate="Y" showAccessEndDate="Y" showDescription="Y" showLinks="Y" orderOfLinks="OLDESTFIRST" howManyLinks="10000" errMsgTemplate="SHORT" productId="ALL" dateFormat="YYYY-MM-DD" showproductcount="N"]

[DAPComingSoon]

[DAPComingSoon showProductName="Y" showAccessStartDate="Y" showAccessEndDate="Y" showDescription="Y" showLinks="Y" orderOfLinks="NEWESTFIRST" howManyLinks="10000" errMsgTemplate="SHORT" productId="ALL" makelinksclickable="N" dateFormat="YYYY-MM-DD"]

[DAPUserProfile]

[DAPUserProfile showFirstName="Y" showLastName="Y" showUserName="Y" showEmail="Y" showPassword="Y" showAddress1="Y" showAddress2="Y" showCity="Y" showState="Y" showZip="Y" showCountry="Y" showPhone="Y" showFax="Y" showCompany="Y" showTitle="Y" showPaypalEmail="Y" showOptedOut="Y" showCustomFields="Y"]

[DAPUpline]

To show affiliate’s/sponsor’s first name:
[DAPUpline showField="first_name"]

To show affiliate’s/sponsor’s last name:
[DAPUpline showField="last_name"]

To show affiliate’s/sponsor’s custom field (say “ssn”):
[DAPUpline showField="custom_ssn"]

More examples and details in the “Shortcode Details” section below.

 —————————————————————————————————————-

Shortcode Details

All of the shortcodes listed in the above “Shortcode Summary” section, are explained here.

Basic DAP Shortcode

[DAP]…private content…[/DAP]

This is the shortest version of the DAP Shortcode. In this version, anything you put between the [DAP] and [/DAP] tags, will be viewable only by a logged-in user.

No other restrictions for the content to be viewed, except that the viewer has to be logged in to your membership site (via DAP). So basically all free and paid members, regardless of which product they have access to, regardless of whether their product access is active or expired, can view the private content.

Full DAP Shortcode

[DAP hasAccessTo=”1,2,3″ errMsgTemplate=”SHORT”]…private…[/DAP]

This is the full version of the DAP Shortcode. All inner tags – hasAccessTo and errMsgTemplate – are all OPTIONAL.

hasAccessTo: Comma-separated list of one or more Product Id’s that you want the user to have access to before they can view the content. So if you enter 3 different product id’s (like hasAccessTo=”2,7,14″) it means “Anyone with access to AT LEAST ONE of those products with the product Id’s 2, 17 or 14. It does NOT mean they have to have access to all of them at once. Access to any one is fine.

errMsgTemplate: This determines the HTML/text of the error message displayed, if user DOES NOT have access to the content being protected.

Values may be Can be SHORT, LONG or “” (empty). NOT mandatory. If omitted entirely from the tag, then the default template used is SHORT.

If you want no error message to be displayed, and want the protected content to silently disappear completely if user does not have access to it, then include the tag, but set it to “” (blank/empty), like this…

[DAP errMsgTemplate=””]…private…[/DAP]

The HTML/text displayed by the SHORT and LONG templates can be configured via the Setup > Templates screen, as shown below.

Examples

[DAP]...private content...[/DAP]

Viewable by Any Logged-in User

[DAP hasAccessTo="1" errMsgTemplate="SHORT"]...private...[/DAP]

Viewable by ANY logged in user (FREE or PAID – doesn’t matter) who is a user of the product with the ID “1” (you can get the Product id from the “Products > Manage” screen). Display HTML/text from the SHORT template if user does not have access to the private content.

[DAP hasAccessTo="1,2,3" errMsgTemplate="LONG"]...private...[/DAP]

Viewable by ANY logged in user (FREE or PAID – doesn’t matter) who has access to EITHER of the Products – 1, 2 or 3. Display HTML/text from the LONG template if user does not have access to the private content.

Member-Specific Content

“For Your Eyes Only”
Let’s say you run a coaching program. You have 10 clients. You want Joe Customer to see a tailor-made custom video meant only for Joe, and Jill Member to see a specific PDF report written specifically for Jill’s business. Now using the new “userId” parameter in the DAP shortcode, you can now protect a piece of content so that only a specific DAP user can see it.

[DAP userId="144"]protected content[/DAP]

In-Page Dripping

DAP Shortcodes now include the ability to specify a “Day” right within the shortcode itself. So you can now publish, say, 10 videos on one page, and you can enclose each video’s embed code with a separate DAP Shortcode that has a different “Day” setting, so the very same page will show 1 video on Day 1, 2 videos on Day 2, 3 videos on Day 3, and so on.

Like this…

[DAP day="1" hasAccessTo="1"]Video 1 Embed Code[/DAP] [DAP day="2" hasAccessTo="1"]Video 2 Embed Code[/DAP] [DAP day="3" hasAccessTo="1"]Video 3 Embed Code[/DAP]

NOTE: Please remember that you may not omit the hasAccessTo field – you must use the hasAccessTo field to specify a product id, because all start “days” for a user are associated with a product.

Hiding Content From Logged-In Members

Starting DAP v4.1, you can now mark content such that it will NOT be displayed to members who ARE logged in. To put it another way, it will HIDE content from members, and show it ONLY to NON-Members.

For example, this could be your sales copy or your buy-button, that you don’t want your logged in members (who may have already purchased the product) to see.

Here’s the shortcode for that.

[DAP isLoggedIn="N"]....content to show only to NON-members... [/DAP]

publicUntil

You can set a date UNTIL which a blog post is public (no protection or rules will be applied from any other shortcode parameters.
[DAP publicUntil="2012-12-31" hasAccessTo="1"]This message will be completely public UNTIL (and including) December 31st, 2012[/DAP]

publicAfter

You can set a date AFTER which a blog post will become public (no protection or rules will be applied from any other shortcode parameters.
[DAP publicAfter="2012-01-01" hasAccessTo="1"]This message will be completely public AFTER (and including) January 1st, 2012[/DAP]

hasNoAccessTo

A much requested feature. You can now specify a list of products that a user does NOT have access to, like this:
[DAP hasAccessTo="2" hasNoAccessTo="1,3" ]This message will appear only to active (current) users of product 2 but don't have access to 1 or 3[/DAP]

startday / endday

Now you can specify “startday” and “endday” in the shortcodes to make the contents stop being shown after a certain end “day”. Previously available “day” variable has been deprecated and replaced by “startday” instead. However, if you already are using it somewhere, it will continue to work as is. However, if you wish to use the “endday” variable, you must now also use “startday” instead of “day”. Very useful for, say, displaying a message on the Welcome page only on the first day.
[DAP hasAccessTo="2" startday="1" endday="1"]This message will appear to you only to users of Product 2, on Day 1 and no further[/DAP]

startdate / enddate

You can also specify actual dripping “dates” (instead of “days”) by using “startdate” and “enddate” in the shortcodes to make the contents stop being shown after a certain end “date”.
[DAP hasAccessTo="2" startdate="2012-01-01" enddate="2012-01-31"]This message will appear to you only to users of Product 2, on between the dates of Jan 1st, 2012 and Jan 31st, 2012 - and no further[/DAP]

Negative Days

“startday” and “endday” can also be a negative number.
For eg., [DAP hasAccessTo="2" startDay="-6" endDay="-3"]Howdy[/DAP]

This basically means, the message “Howdy” will be shown starting 6 days before the “Access End Date” of the user’s access to the product with Id “2” (specified in hasAccessTo). So you can use this to display a special message – or specially priced offer (buy button) – for those whose access has not yet expired. Last day (same day of access end date) is day 0. Day before that is -1.

Error Message From File

You can now specify a file name whose contents are to be used as error message. Use the existing errMsgTemplate field, but add a “file:…” to the beginning, and make sure the file name is a fully qualified URL starting with http:// and your domain name. So you can say…
[DAP hasAccessTo="2" startday="1" endday="1" errMsgTemplate="file:http://YourSite.com/customMessage.html"]This message will appear to you only today[/DAP]

[DAPUserLinks]

Allows you to heavily customize how the links are displayed when you use the merge tag %%USERLINKS%%…

[DAPUserLinks showProductName="N" showAccessStartDate="Y" showAccessEndDate="Y" showDescription="Y" showLinks="Y" orderOfLinks="NEWESTFIRST" howManyLinks="10000" errMsgTemplate="SHORT" productId="ALL" dateFormat="YYYY-MM-DD"]

[DAPComingSoon]

Allows you to display links that are coming soon.

[DAPComingSoon showProductName="Y" showAccessStartDate="Y" showAccessEndDate="Y" showDescription="Y" showLinks="Y" orderOfLinks="NEWESTFIRST" howManyLinks="10000" errMsgTemplate="SHORT" productId="ALL" makelinksclickable="N" dateFormat="YYYY-MM-DD"]

[DAPUserProfile]

Allows you to selectively display profile fields on a page. Just set the profile field that you don’t want shown to “N” in the tag below.

Default is “Y”. So Leaving out the text showLastName=”Y” entirely from the shortcode, is the same as setting it “Y”, which means it will be displayed.

So just entering the text [DAPUserProfile] into a page, will show ALL fields.

And to not show say, Phone and Fax, you would do something like this:

[DAPUserProfile showPhone="N" showFax="N"]

So all other fields will be displayed, except those two.

[DAPUpline]
This shortcode shows a user their referring Affiliate’s (a.k.a Sponsor’s) information. So when a user visits the page that has this shortcode, it will display information of that user’s referring Affiliate – either from cookie (if exists), or if they’re already a member, then their current Affiliate’s information. And if neither the cookie is set, nor the user has an Affiliate attached to their account already, then it will show the info of the DAP Admin). So you can use it to show the user information of the person (affiliate) who referred them to the page. Think of it as a “Your Sponsor” tag.

To show affiliate’s first name, use this:
[DAPUpline showField="first_name"]

To show affiliate’s last name, use this
[DAPUpline showField="last_name"]

[DAPUpline showField="user_name"] [DAPUpline showField="email"] [DAPUpline showField="address1"] [DAPUpline showField="address2"] [DAPUpline showField="city"] [DAPUpline showField="state"] [DAPUpline showField="zip"] [DAPUpline showField="country"] [DAPUpline showField="phone"] [DAPUpline showField="fax"] [DAPUpline showField="company"] [DAPUpline showField="title"] [DAPUpline showField="paypal_email"]

For Custom fields…
[DAPUpline showField="custom_customfieldname"]

4

User & Product Statuses

DAP assigns a status for the User itself (at a global, account level), as well as a User/Product level (specific to the user's access to that product).

So there's the User Status and then the User/Product Status

For eg., the User Status may be "Active", but a specific User/Product status may be "Inactive" – which means user can log in to their account, receive emails, etc, but cannot access any content that is part of this specific product (though they can access all other products they may have, that are "Active").

The bottom-line is this: In order for a user to access his/her account, and all the content in the Products that he/she's purchased, all the statuses have to be Active.

So here are the possible statuses, and what they mean.

User Status

These statuses apply to the User's account itself.

Inactive

If the user's status is inactive, then that means the user's entire account is inactive. User will not be able to even log in to their account. All outgoing broadcast and autoresponder emails will "exclude" them from the list, and they will not receive any emails from the system.

Active

Account is accessible, all emails are being sent.

Unconfirmed

They've just signed up for a product that requires "Double Optin". Which means, unless they "confirm" by clicking on the double-optin link, their account will not become active. Please note that once a user has already confirmed the double-optin link for one product, then their "User" status automatically becomes "Active". So even if they go on to sign up for another double-optin product, then their User status will never again change to "Unconfirmed" (unless specifically set so by the DAP Admin). For all future double-optin products, it is this user's "User/Product" status that will be "Unconfirmed", while the main "User" status remains "Active".

 

Locked

When an account receives login attempts from more than the number of IP addresses set in the "Setup > Config > Advanced > Max. # of User Logins From Different IP`s" field, then that user's main User status is changed to be "Locked". This is very similar to the "Inactive" status, except named different just so admin can distinguish between "Locked" and other users.

 

User/Product Status

These statuses specifically apply to a User's access with relation to a specific Product.

Inactive

User cannot access any content that is part of this product. However, User may access other products whose user/product status is "Active".

Active

There are no restrictions for this User to access content that is part of this product (of course, only whatever the user is eligible to see, based on the drip setup).

Troubleshooting Login Errors

Problem: When you go to http://YourSite.com/dap/ , you get redirected to a "Page Not Found – 404" error page.

Solution: This is happening because in DAP Config, you probably set up an invalid URL to be the default login page. So do this:

  • First, log out of DAP by going to http://yoursite.com/dap/logout.php (manually type that in to your browser)
  • Now log in to DAP via DAP's special login page – http://YourSite.com/dap/login.php
  • Go to "Setup > Config > Advanced" screen
  • Then where it says "Location of your login page (eg., if using WordPress). Should start with a forward slash (`/`)" – enter a valid URL there. Before entering any URL there, visit the URL separately in a separate browser tab (or window) and make sure you can actually get to it, and that it has a login form there. Then put that URL in to the above field, and click on "Update".
  • Now in a separate browser (totally different browser) where you are not logged in to DAP or WP, try to go to http://YourSite.com/dap/ and see if it redirects to the right page. If not, revisit the steps above, and double check the login URL, that's all.
12

DAP Shopping Cart Checkout page

Here’s a screen-shot of how the DAP checkout page looks if you use the DAP internal shopping cart.

You can always add your own header (/dap/inc/cartheader.php) and footer (/dap/inc/cartfooter.php) to the checkout page.

 

 

1SiteAutomation.com Upsell Express

DAP integrates with 1SiteAutomation.com‘s (our private label of 1shoppingcart) Upsell Express.

So if you are using 1Shoppingcart or our private label 1SiteAutomation.com to accept payments, then you cannot use DAP’s own free Upsell-Tree plugin. You will have to sign-up for 1SiteAutomation.com’s Upsell Express add on, which has a monthly fee associated with it.

Don’t have a 1shoppingcart account yet, and thinking of signing up for one? You certainly don’t want to do that till you check out our “Get DAP For Free” offer.

2

DAP-1SC Login Xpress

DAP Supports instant auto-login to the member’s area immediately after completing the 1ShoppingCart (or private label) purchase. We call this Login Xpress with 1ShoppingCart (Read more about Login Xpress)

The documentation below will show you how to setup 1ShoppingCart and DAP, so that your buyers can be automatically logged in to your “Member’s Area” upon completion of their purchase.

Note About Processing Recurring Orders via 1SC

If you only sell ONE-TIME products at this time, then the Login Xpress flow below is all you will need to setup as far DAP & 1SC integration is concerned.

If you are selling RECURRING products via 1SC , but DO NOT WANT your users to be automatically logged in to the “Members’ Area” right after their purchase, and you prefer sending them their membership login info (email & password) via email, then you DO NOT need to read this post any further – simply head over to this post: 1ShoppingCart Recurring Payment Processing via Email

But if you sell RECURRING products via 1SC and you DO WANT your users to be automatically logged in to the “Members’ Area” right after their purchase, then continue reading this post for Login Xpress setup.

Login Xpress Setup

1) Set up your sales page as you would normally do when accepting payment through 1ShoppingCart.

Make sure to use the exact same Product Name in 1SC as well as within DAP.

So, if you set up a product called “Platinum Members” within DAP, then use the exact same name “Platinum Members” as your 1SC  product name. In fact, just to be sure, copy the product name from DAP and paste it into the product name field within 1SC (or vice-versa). That way, there will be no typos.

2) Log in to your 1ShoppingCart account.

Go to Products > Manage Products. Edit the Product you are setting up.

Go to the “Links” tab of that Product.

Set up the Thank You URL to point to this DAP script on your site, as shown below:

http://YourSite.com/dap/dap-1shopcart.php?cartId=SecretKey

YourSite.com should be replaced by the name of your site

SecretKey should be set to the same value that you set in  DAP Dashboard > Setup > Config > Secret Key For Payment Processing

This secret key can be alphanumeric. No special characters or spaces.

For eg., if you set Secret Key For Payment Processing in DAP to be 12345

Then your 1ShoppingCart Thank You URL would look like this:

http://YourSite.com/dap/dap-1shopcart.php?cartId=12345

DAP Secret Key Setup (under DAP Admin > Setup > Config)

3) Now open a brand new browser session where you are not logged in as DAP admin or WP admin.  Complete a test purchase using an email id that is not already in your DAP.  If the integration worked correctly, then a new user account will automatically get created in DAP, and you (the buyer) will also be automatically logged in to DAP, and will be redirected to one of the following URL’s:

a) If this buyer has access to just 1 product, then user will be redirected to the Post-Login URL set up under that Product, at DAP Admin > Products > Manage

-OR-

b) If this buyer has previously purchased other products, then for security reasons, buyer will be redirected to the login URL that you have set up under DAP Admin > Setup > Config > Login URL. And at the same time, the buyer will be sent the Welcome Email from the Product’s settings.

Redirecting To A Custom URL After Checkout

The above setup will log new members right into the member’s area immediately after completing their purchase through your 1SiteAutomation.com or 1Shoppingcart check out page.

But if you wanted them to be redirected to a different page of your choice after the purchase, then set up the thank-you URL like this:

http://YourSite.com/dap/dap-1shopcart.php?cartId=SecretKey&redirect=yoursite.com/another-page/

So basically you are just adding the text in red to the end of the standard DAP/1SC thank-you page URL.

Now note that even though user is being redirected to “another-page” in the above example, they have been logged in to your membership site already. So if you publish a link to your member’s area somewhere on “another-page”,  then they can go right to that page without having to log in, because they’re already auto-logged in at this point.

NOTE:

If you are setting up a recurring subscription product, then after completing the above Login Xpress set up, next step is to set up DAP to process RECURRING payment notifications from 1SC as described here.

Un-Installing & De-Activating DAP

While DAP is extremely well integrated with WordPress, all of that integration is achieved via code, and not the back-end database.

DAP stores all of your member and product and content information in its own database tables. It does not store anything in your wordpress database, or modify it in any way.

So when you stop using DAP, your wordpress blog (i.e, data) goes back to being what it was before DAP was ever installed. It’s like DAP was never installed. So disabling or removing DAP from your site will not affect your web site or blog in any way.

De-Activating DAP

It is ok to de-activate the DAP-WP-LiveLinks WordPress plugin either temporarily or permanently.

You will not lose any of the data stored in the DAP database. Everything will remain intact. Only thing to note is that de-activating the plugin will “un-protect” all protected content on your blog during that time, and all of the protected content now becomes “publicly viewable”. You may enable all of the content protection simply by re-activating the plugin.

Un-Installing & Removing DAP

For this, there are couple of steps:

  1. De-activate the DAP-WP-LiveLinks plugin
  2. Delete the DAP-WP-LiveLinks folder from wp-content/plugins/
  3. Open the .htaccess file in your root folder of your web site. You should see a few lines in there related to DAP. It should look something like this…

    #—– START DAP —–
    RewriteCond %{REQUEST_FILENAME} -f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteCond %{REQUEST_FILENAME} (.*)/wp-content/uploads/(.*)
    RewriteCond %{REQUEST_FILENAME} !(.*)(\.php|\.css|\.js|\.jpg|\.gif|\.png|\.txt)$
    RewriteRule (.*) /dap/client/website/dapclient.php?dapref=%{REQUEST_URI}&plug=wp&%{QUERY_STRING}  [L] #—– END DAP —–

  4. Just delete all of the above lines, and re-upload the .htaccess file back to your site root folder.
  5. Delete the “dap” folder from the root of your web site.
  6. If you wish to also delete the dap tables from your database, then you must log in to your web hosting control panel, go to your database via the “phpMyAdmin” link, and then “drop” all of the database tables that start with “dap_”. That will delete all the DAP database tables and the data within.
  7. Finally, go in to your web hosting cpanel, go to the “Cron” section, and remove any cron jobs related to dap (you’ll see towards the end of the cron job text fields, that the script running will either be dap-cron.php and/or dap-emailorder.php.

Unplugging Your Payment Systems

Make sure your payment systems (like Paypal and Authorize.net) and shopping carts (like 1ShoppingCart or Infusionsoft) are no longer notifying DAP when payments come in.

Go to our documentation section, look for the setup documentation specific to your payment processor, and then do the opposite – basically just un-do whatever is in the setup – the reverse of whatever is the actual setup process.

 

 

DAP does not modify any wordpress tables. So deleting DAP tables won’t affect your wordpress installation.
1 … 15 16 17 18 19 … 29