1) Update DAP Setup > Config -> Secret Authorization Key to be…

YourGCmerchant_id|YourGCmerchant_key

2) Point the Google Checkout IPN handler to

http://yoursite.com/dap/dap-gc-responsehandler.php

(replace yoursite.com with the name of your site).

3) Create a DAP product and make sure the item name that your GC Item Name exactly matches the DAP Product Name.

That’s it!

NOTE

You will find a file by name dap-gc-responsehandler.php in your dap folder.

Use this file as is, with no changes, during testing. Nothing to change.

But once you’re ready to go live, open the file, and find the line below:
$server_type = “‘sandbox”;

And change it to:
$server_type = “‘production”;

1) Go to DigiResults.com “Manage” products tab at https://www.digiresults.com/manage/products

2) Click on the Product Name

3) Click on Product Details tab

4) Click on Advanced Settings and set the Direct Receipt URL to point to the dap script on your site…

http://YOURSITE.com/dap/dap-digiresults.php

5) Create a product in DAP and make sure the dap Product Name exactly matches the digiresults Product Name.

That’s it!

Now run a test purchase via digiresults and see if the account gets created in dap automatically.

Here’s what you need to do to disable the standard vB login form at the top-right corner of your forum pages, and customize it so that you force your members to log in via the DAP login form, so that they’re logged in to your membership site as well as DAP.

1. Log in to VB Admin control panel at http://yoursite.com/forums/admincp/
2. Go to Styles & Templates > Style Manager > Default (or whatever style you’re currently using)
3. From the big list on the left, select the “header” template. Then on the right, under the “Controls” section, click on Edit
4. On the resulting page, copy the full code from this text file and paste into the main “Template” body, and click on “Save”
5. Next, download the file forums/register.php from your server, to your desktop and save the original copy somewhere safe.
6. Replace the contents of that file with the contents of this text file.

That’s it!

Starting v4.2.1, DAP now integrates with Premium Web Cart (PWC)

PWC=>DAP integration is very simple to set up.

NOTE:

• If your DAP version is 4.2 or earlier, you must upgrade to DAP v4.2.1 & LiveLinks v1.7.
• If you are already using DAP v4.2.1, then download the very latest dap_v4.2.1 zip from the member’s area, unzip the contents to your desktop, and upload just the dap-pwc.php (within the main dap folder on your desktop) to the dap folder on your site.

Integration Steps

• Login to your PWC account.
• Go to Cart Settings > Advance Integration.
• Select PWC IPN tab.
• Set the PWC IPN URL to http://yoursite.com/dap/dap-pwc.php  (Note: replace yoursite.com with the name of your site)

User Flow

• Buyer clicks on the buy button (button created within your PWC account and published on your sales page).
• Buyer completes the payment successfully and is transferred to the thankyou page.
• PWC notifies DAP via IPN about the purchase.
• DAP automatically creates the member account, and sends thank-you email (configured in your dap products page) with login info to the buyer.   NOTE: Make sure to setup the thankyou email in the DAP products page for all the products you sell via DAP.
• When the user logs in to their membership area, they will be redirected to either product-level logged-in URL or global logged-in url based on whether they have access to just 1 product or multiple products. The product level logged-in url is used if the user has access to just 1 product. The global logged-in url (under dap setup -> config -> advanced -> url to which user is redirected upon login) is used when user has access to multiple products.

Note: You can create a member’s area and redirect users to that page upon purchase.

There are two main items that need to be addressed when it comes to a member wanting to Upgrade or Downgrade their Subscription from one membership “level” (a.k.a “Product” in DAP) to another.

1) Modifying the actual recurring payments to reflect the new amount

2) Giving them appropriate access as per the upgrade (or downgrade)

So let’s see how both of these are accomplished.

1) Modifying Recurring Payments

You do need to take some manual action for this. The way to do it is….

• Ask your members to sign up for the new product/level/subscription separately, like it were a new sign up
• Cancel their old subscription manually. When using Paypal standard, this can be done by both you (as the admin) and the member themselves. But with all of the other payment solutions, you (the admin) will have to log in to the payment gateway (Authorize.net or Paypal Website Payments Pro) and manually delete the member’s old subscription). DAP will not automatically remove user’s old subscription profile in your payment gateway.

2) Giving your member access to new level

Set up automation rules using DAP’s Product Chaining feature, so that if they sign up for one Product (or “level”), they’re automatically removed from another Product (or level).

So if they are currently signed up to your “Gold Membership”, then when they sign up afresh for the “Platinum Membership”, then set up a Product Chaining rule that says, “If member signs up for Platinum Membership, then remove them from Gold Membership”. This is just to make sure that they don’t have access to two products (or “levels”) at the same time.

DAP offers a number of affiliate statistics on the “Affiliates > Reports” page.

Here’s how it looks as of DAP v4.2.1.

1) Email Id of Affiliate

This is the field where you would enter the email id of an affiliate, if you want to generate a report specifically for an affiliate. If you leave it blank, the report will include all affiliates.

2) “From” & “To” Dates

By default, if you leave these fields blank, then DAP will assume “today’s” date – i.e., the date whenever you’re viewing this page.

3) View Performance Summary

This is the most detailed report available. This is the report being viewed in the above screenshot. For a given time period, for a given number of affiliates (“all” affiliates if (1) is left blank above), it shows…

• Affiliate Id
• Full Name
• Email id
• Clicks generated during selected period
• Referrals generated (includes total of both Free and Paid referrals): If the referred member actually bought something, it constitutes a “Paid” referral. If they simply signed up, say, for your free newsletter or free report or free product, then it is counted as a “Free” referral.
• Commissions Earned: This is the actual amount credited to the affiliate’s account during the selected period
• Sales Generated: This is the amount of the actual sale (purchase) generated for your membership site.
• Earnings Per Click (EPC): This is an indicator of how well your web site is converting clicks into signups/members. So if an affiliate sent you 100 clicks (on their affiliate link), and 5% of them signed up for your “FaceBook Secrets” membership product by paying $10 each, it means a total revenue of $10 x 5 = $50. And if you were paying 30% affiliate commissions for the product, then the affiliate earned $15 in total.Total clicks sent: 100
  Total affiliate earnings from those 100 clicks: $15
  Earnings Per Click (EPC) = $15/100 = $0.15 – which means, 15 cents per click.The higher the EPC, the easier it will be for you to attract other JV partners and super-affiliates.

4) View Earnings Details

This shows the breakdown of each purchase referred by each affiliate. It’s a detailed view of the affiliate earnings, that lists each and every transaction (order) in the system that was referred by affiliates, all generated for the selected time period. It displays…

• Affiliate Id
• Full Name
• Email Id
• Product (name) that was purchased by referred buyer
• Referral Date (when affiliate was associated with buyer)
• Date/Time of actual transaction
• Trans Id: This is the transaction (order) id for the actual purchase
• Earning Type (L: Lead, S: Sale): Says what type of a commission credit it was – whether it was a “Pay Per Sale” credit or a “Pay Per Lead” credit.
• Id of User Referred: This tells you the actual user id of the buyer who was referred by the affiliate.

5) View Payments

This shows all payments made to affiliates during the period.

6) Refund Period

This is a config setting that you can change in Setup > Config. This is what drives which orders are picked up for affiliate payment. See this article for more details.

7) View Due Payments as of <date>

This is the MAIN button you should click to start the process of paying your affiliates each month (or however often it is that you pay affiliates). When you click this button, it will show you a report (see screenshot below) of commissions owed on all orders in the system UNTIL  X days ago, where X is your “Refund Period”.

So if today is 10/01/2011, and you have a refund period of 60 days, then DAP will only consider orders prior to 60 days as of today. Which means, orders up to 08/01/2011 (of course, depending on how many days in a month, you may not exactly end up with 08/01/2011, because it goes an actual 60 days back from today – and sometimes, the report will stop at the 2nd or 3rd day of the month – like 08/03/2011. But that’s ok, don’t worry about it). You just focus on paying your affiliates on whatever day you wish to make the payment.

So when you click on this button, DAP will bring you a summary report of all affiliates, and how much they’re owed today, for all transactions referred by them as of 08/01/2011 (as per this example).

And when you click on the “Export These Affiliates For Payment” button shown in the screenshot above, DAP will select and mark those affiliates as being exported for payment.

And DAP will show you Paypal Mass-Pay Ready text report, with the affiliate info and the commission amount info already filled in and ready to go. If you’re paying via Paypal Mass-Pay, then all you need is this file. See this post for details.

NOTE: Being exported for payment doesn’t mean that you’ve actually paid them. Exporting affiliates for payment only means that DAP has now “set aside” those affiliates for payment, and you still need to tell DAP that you’ve actually paid your affiliates.

This is important, because you might export affiliates for payment on the first of the month, but it may take you a day or two (or 10) to actually make the payment – especially if you’re sending out Checks.

So once you’ve made the payment either through Paypal mass-pay, or by mailing your affiliates physical checks, then you need to tell DAP that you’ve actually sent out the payments, which is what you’ll do in the step below.

8 ) Mark Affiliates from <export> as Paid

This is where you will select the most recent export from the drop down (see #8 in first image at the very top), and click the “Paid” button. This is what actually lets DAP know that you’ve actually made the payment, and only after you do this, will the affiliates see the payment show up in the “Payments” section on their “Affiliate Info” page.

9) Archived Reports

This is just a report that shows you past commission payment exports.

If you have a coaching program, or have clients for whom you’re doing custom work (like if you were a CPA or a web designer), and want to publish content that is available to and downloadable only by that client, then there are THREE ways in which you can do Member-Specific Content in DAP.

1) BEST SOLUTION: Using a combination of a special page for each member PLUS DAP’s “For Your Eyes Only” Shortcode

2) Creating Separate Products for each Member

3) Using DAP’s “For Your Eyes Only” Shortcode

Let’s take a look at each one in detail.

1) BEST SOLUTION: Special page for each member PLUS DAP’s “For Your Eyes Only” Shortcode

This is partly manual, partly automated, but is the absolute best solution for multiple reasons, as explained below.

1) For each new member, you would create a separate page. So, for Joe Customer, you would create a new page in WP – http://YourSite.com/joe-customer/

This page would be created after someone has become a member, of course. But creating a WP page for every member will probably take you about what, 30 seconds? So it’s not going to be a big deal (unless you wish to make it one

2) Then, assuming Joe Customer’s “userid” in DAP is 144 (you can find this out on the Users > Manage page). So within the above new page, you would add the following shortcode…

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

(See DAP’s “Member-Specific Content” Shortcodes )

3) You can start adding any amount of private content between the shortcode start and end tags (where you see protected content above).

4) You can use a simple, free plugin like Exclude Pages to make sure the customer’s page http://YourSite.com/joe-customer/ does not show up in any of your menu’s. Even if it did, it’s not like anyone else can see the contents of the page – only Joe Customer – after he’s logged in to DAP – can see the contents of the page. So it’s secure from everyone else.

2) Separate Products for each Member

Here, you would create separate products, one per member – and only give that member access to that product. The advantage here, is that you can protect the entire page (not just the content section) and make it available just to that one client, so you can be a lot more creative with this page, use special templates, add sidebar widgets that show content just for that client, use the commenting system to communicate back and forth with the client.

So if you had a client named John Customer, then you would create a DAP Product by name “John Customer”, then take John’s email id and give John access to his product.

And within this DAP Product, you would’ve protected files, pages and posts that only John should get access to. So since only John has access to the product, only he can get access to the content protected as part of this product.

Obviously, it takes a few minutes of additional setup per customer to create a DAP Product specifically for him, but then the few extra minutes of creating a DAP Product would be nothing compared to the few hours (or tens of hours) that you’re actually going to be taking to create the actual custom content for John. So it’s a very small overhead compared to the whole process, where you are actually creating custom content for each member.

3) No special pages, just DAP’s “Member-Specific Content” Shortcode

If you wish to automated this a bit more than Option #2, then one way is to implement this is using DAP’s “Member-Specific Content” Shortcodes, which look like this:

Using the “userId” parameter in the DAP shortcode, you can now protect a piece of content so that only John Customer (who has the user id “144″ in your membership site) user can see it.

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

So on a single page, you may publish a number of these shortcodes, with content meant only for specific members protected within those shortcodes.

And doesn’t matter which one of your members visits the above page, they will all only see content intended only for them, and will be unable to see content intended for others.

So those are the three ways in which you can create Member-Specific Content.

Using a “cache” plugin for speeding up your site is like putting band-aid on a gaping wound. It’s only a temporary fix, and not a real long-term solution.

Plus a cache plugin has its place, but it’s certainly not for a membership site, where DAP will need to make calls to the database to figure out who’s viewing the content, are they a member, what products have they purchased, what content do they have access to, etc.

If you want to speed up your web site, you must address the core issue, which is — your web site is getting more traffic than your web server (web hosting account) can handle.

So here are a couple of ways in which you can speed up your web site:

• The easiest thing you can do is to revisit all of your plugins that you have enabled. Remember that every single plugin adds some overhead to (read “slows down”) your web site or blog. So use only as few plugins as you absolutely must. With so many cool plugins available freely for WordPress, it is very easy to get carried away, and install tens of plugins, most of them adding very little value, but sometimes causing the most overhead in terms of server resources. So keep only a bare minimum of other plugins (some social plugins are a real pain – making calls to third-party web sites to get their information from).
• If you are hosting on a shared (a.k.a “cheap”) web host paying just a few dollars a month for hosting, then your web site is basically competing for server resources (like memory and bandwidth and database access) with possibly tens (or even hundreds) of other web sites on that same server (many may not belong to you, but to others with whom you are sharing the server – and hence the name “shared hosting”).Search for the keywords “digg effect” or “slashdot effect” on Google, and you’ll see how many WordPress sites crash when a link to the site appears among the top results in popular social sites like Digg.com, Reddit.com or Slashdot.com.

  If your traffic levels have outgrown your server, then the best thing you can do is to upgrade to a bigger server, or get a Virtual Private Server, or even get a dedicated host, depending on your budget. See our recommended web hosts list.

DAP has a “Smart Login” feature, where the login process will work slightly differently under different conditions, all designed to make the user-experience for your member more smooth and consistent with general log in standards around the web.

So let’s see the various possible login locations in DAP.

But first, it is important to note that DAP has two main types of logins.

Primary Login

This is where it is considered a “generic” login by your member. For eg., a member came to your web site, and then just generally wants to log in to the member’s area – so they have no “context” – it’s NOT as if they were trying to view a specific page or post, got challenged with a login form, and then logged-in from there. That makes this a “Primary Login“.

Examples of this are…

a) You have a dedicated login page, like http://YourSite.com/login/ – which is what you’ve entered in to “Setup > Config > Login URL“. The body of this page has the DAP merge tag for the login form, which is %%LOGIN_FORM%%

b) Login/Logout Widget on the home page of your web site. This is also considered a primary login, because they just came back to your site, and just wish to log in to their member’s area to see what’s new.

Secondary Login

This is a log in action that HAS “context”. Say, a member landed deep into your site (not the home page, not the dedicated login page) and tried to log in from, say, the widget on the side-bar, or were challenged by the “In Page Error Message” that says something like “Sorry, you must log in before you can view this content” and are presented with a login form right on that very same page. They were trying to read something before they were asked to log in first – which means, they must be returned to the same page they were trying to view BEFORE they were asked to login. So that makes this a “Secondary Login“.

Examples of this are…

a) Login/Logout Widget on any page EXCEPT the home page.

b) Any custom “Error Page”, where you have inserted the DAP merge tag for the login form, %%LOGIN_FORM%%.

c) DAP’s “In-Page Error Message” which says “Sorry, this is private content – you must log in first before you can view this”.

So now that you know what’s a Primary Login and what is a Secondary Login,

Redirection Rules

Based on whether it’s a Primary Login or a Secondary Login, your member will be redirected to a different location.

1) If it is a Primary Login action, then…

a) They’re taken to the “Post-Login URL” if set at a Product-level AND they have access to just one Product.
b) They’re taken to the GLOBAL “Post Login URL” (under Setup > Config) if you have NOT set anything at a Product-level, OR if they have access to more than one Product.

This scenario is the only one where the Post-Login URL is ever used (whether it’s the Product-level or Global-level).

1) If it is a Secondary Login action, then…

They’re always redirected back to the same page they were on (or were trying to access) before they were challenged to log in first to view the content.

Bottom-line:

Primary Login is predictable, and you (the DAP Admin) control where they go right after they login.

Secondary Login depends on “context”, and they’re taken back to whatever page they were before they logged in.