But if you want your Aweber list to be single-opt-in, then you can use the Aweber webform (instead of DAP sign-up form) and follow the steps below to integrate DAP with Aweber.

1. Go to DAP admin panel -> manage products page.

2. Note down the product Id of the product to which you want to signup the users.

3. There is a file called dap-aweber.php in your /dap folder. Make a copy of that file and call it dap-aweber-<productId>.php. Replace <productId> with the product Id you noted in step 2.
If the productId = 2, then you will end up with a file called dap-aweber-2.php.

4. Open this file (dap-aweber-2.php), and change this line:
$default_product_id = 1; //Change this to any product id from DAP

So, in this example, change it to:
$default_product_id = 2; //Change this to any product id from DAP

Upload this file back to /dap folder on your site.

3. Now login to AWeber, select your single-opt-in list in AWeber -> Webform -> click on ‘Go to Step 2′ towards the bottom of the page.

http://screencast.com/t/ZTE0MDhhYTY

Click on the thankyou page dropdown and select ‘custom page’.
Set the thank you Page URL to http://<yoursite.com>/dap/dap-aweber-<productId>.php
Replace <yoursite.com> with the name of your site. Replace <productId> with the product Id you noted in step 2.

4. Use the Aweber web form for signing up customers (instead of dap direct signup form).

That’s it.

Everytime a users signs up via the aweber web form to your site, they will automatically be added to DAP.

You can configure the welcome/thankyou message in DAP to send out the dap login id and password
OR
You can leave the welcome/thankyou message in DAP empty. Configure DAP to generate a default password (DAP Admin -> Setup -> config -> Advanced) as shown in the screencast below and set up an autoresponder in Aweber so when the users signup via the Aweber form, they can receive their dap id/password details via Aweber directly.

http://screencast.com/t/MjY0NGI3

If you wish to customize the look & feel or text of the form, then rename the file…

wp-content/plugins/DAP-WP-LiveLinks/DAP-WP-LoginForm.html

To…

wp-content/plugins/DAP-WP-LiveLinks/customDAP-WP-LoginForm.html

Basically you are adding the text “custom” to the beginning of the file name, that’s it.

And this new file will also reside in the same directory.

Once you have this new file in the directory, DAP will ignore the old, default file, and will only use your new custom version.

Any time someone gets access to PRODUCT A (either through direct signup, manual admin add, or purchase), then you can automatically give them access to PRODUCT B. And you can select whether they get PAID access to PRODUCT B or not.

Similarly, when someone is removed from PRODUCT A, you can also tell DAP to automatically remove their access to PRODUCT B.

Very useful for bundling products.

Product Access Automation

User signs up as free user to PRODUCT A.

Later on, user buys PRODUCT B (which is, say, paid version of PRODUCT A).

If you set up Product Chaining, then you can automatically remove them from PRODUCT A when they purchase PRODUCT B. So when you send an email to all PRODUCT A users asking them to purchase access to PRODUCT B, then you won’t be sending emails to those who have already purchased PRODUCT B.

Click on image below to open full size in a new window.

This feature basically allows you to put all of the Product-specific details (including links available to the member as part of that Product) on a specific WordPress page.

Here’s how it works:

1. Go to DAP Dashboard > Products > Manage

2. Select the Product for which you wish to generate the Product-specific details page. Note down the Product Id (it’s a number as shown below)

3. Create a new WordPress Page – give it any title you want. Put in the text…

%%PRODUCT_DETAILS_<insert-product-id>%%

So in the above example, since the Product Id is “1″, the merge code becomes:

%%PRODUCT_DETAILS_1%%

Publish the page.

4. When you view the page, it will show the product’s details.

That’s pretty much it as far as creating the Product details page is concerned.

Where to use this

Starting DAP v3.8, you can now take the permalink for this above page and enter it into the “Logged-in URL” field of the Product. This field is basically for specifying a Product-specific URL for showing users right after they login. So that way, when someone purchases this product, and logs in to your membership site, instead of showing the default member details page, you could show them just a product-specific page.

• Log in to your web hosting control panel, go to “phpMyAdmin”, select your WordPress database (which is where the DAP tables are also installed, by default)

• Do an “Export” of just the DAP tables. Select the “SQL” option and select “Save as File”. All DAP database tables start with the text “dap_”. Save this file on your desktop – let’s say you call it “dapexport.sql” (it could also be “dapexport.txt” – does not matter what the exact extension is – .txt or .sql).

• Make a back up of the dap-config.php file (located in the “dap” directory on your old site/domain) on your desktop

• At your new site, install WordPress
• Copy the database info from your new blog’s “wp-config.php” to the “dap-config.php” file stored on your desktop.
• Then log in to your web hosting control panel of your new site, go to “phpMyAdmin”, select your WordPress database, go to the “SQL” tab, open the export file from above (dapexport.sql), copy the contents, paste into the SQL tab and hit “Go”. All dap data from your old site is now on your new site.
• Upload all dap files to your new site (don’t do full installation – just upload the files).
• Also upload the LiveLinks files to wp-content/plugins/ .
• Upload the new dap-config.php file from your desktop to the “dap” folder on your new site.
• Log in as WP admin, and activate the LiveLinks plugin. It should give you a warning that DAP is already installed. That’s ok, that’s what we want it to say.
• That’s it. DAP is now moved over from your old site to your new site.
• Log into your DAP Dashboard using your old DAP admin login info, and you’re all set.

Pre-requisites for Importing Users

1) You must have already created the Product into which the users will be imported

2) The user list has to be in a CSV (comma separated) format (one user per line), with the exact format being:

Email,FirstName,LastName

LastName is optional. So your user list could have just

Email,FirstName

Example:

Joe@example.com,Joe,Customer
Jill@anothersite.com,Jill
Bob@another.com,Bob,Member

How to do the actual import

1. Go to Users > Add > “Bulk-Add Multiple Users To A Product”

2. Paste your CSV list into the large text area

3. Select the Product into which you want to import the users

4. Check the “Mark Users as Paid” checkbox if you want them to have “Paid” access to the content (just as if they are actual paying members). If you don’t check it, they will all have access as a “Free” user (instead of a “Paid” user), which means they will only have access to content within the Product that you have marked as “Free”.

5. Click on the “Bulk Add Users” button.

That will first save this entire list as a CSV file in your /dap/admin/bulk folder on your site.

And then, the next time the Hourly cron (dap-cron.php) runs, it will add them one by one to the product, and send them emails as per your Product set up.

So if your Product has the “Thankyou-Email” subject and body filled out, it will individually send out each of the users that thankyou email.

DAP is not an email service (like, say, Aweber).

DAP is just a script – a tool, like Microsoft Outlook or Thunderbird – that simply sends out email using your web host’s email server.

It is your web host’s mail server that actually sends out the email to the recipient. So once DAP sends out the email, it has no control over what happens next.

It’s just like when you put your (regular mail) letter in the mailbox (post box). It is then up to the Postal Service to actually pick up your letter, and deliver to the destination address.

So if the emails that DAP sends out don’t get delivered to your recipients, there could be more than one reason for that.

Server Blacklisting

If your inexpensive (read as cheap shared web host is hosting a large number of sites on one server, and one of them knowingly sends out spam (or mistakenly gets flagged for spam), that will put the email deliverability of every web site on that server in jeopardy, because your site now shares the same IP address as that of an “alleged” spammer.

So your emails get sent to junk/spam folder by Gmail and Yahoo. Or worse, they just totally disappear into the ether.

Hourly Email-Sending Limits

Almost all shared hosts have hourly email sending limits. For example, DreamHost has an outgoing limit of 300 emails per hour. Which means, a total of only 300 emails can be sent out per hour through any web site hosted on DreamHost. All of the following count towards the 300 limit:

• Emails sent by any scripts on your site – like DAP
• Your WordPress blog notification emails
• Your WordPress admin emails,
• WP forgot password emails,
• WP comment notification emails,
• Forum notification emails,
• Forum emails sent to each other by your users,
• Forum-software Admin notification emails,
• Support software user and admin notification emails
• Tell-a-friend emails
• Viral-inviter type emails
• Emails sent through Outlook or Thunderbird where you have set the outgoing SMTP server to be your web site’s SMTP server
• Emails sent by others using the same SMTP server to send out emails-  like your business partners, employees, etc
• DAP User welcome emails, Payment notification emails, Forgot password emails, Autoresponder emails, Broadcast emails, etc

So do you see how quickly you can go over that hourly limit of 300 emails per hour?

But here comes the worst part

Once you go over that limit, any emails that are actually sent by you or the scripts running on your site, will not actually result in any kind of error. The mail server will respond by saying that the email(s) has been sent successfully, but in reality, on the backend, it quietly “snuffs out” the email. Which means, it doesn’t go anywhere – just gets sent to a “blackhole”. So you keep thinking that you sent out the email. DAP keeps thinking it has sent out the email. But in reality, the emails never actually get sent.

This is the same as you actually putting your letter into the mailbox at the Post Office. But then, imagine this: The postal worker who comes to pick up your mail, quietly goes to the back of the post office and dumps it all into one giant trash can, and destroys all of the mail. So you’re thinking you actually mailed out that important check to pay your utility bill. But the utility company never gets your check, and they slam you with a late fee.

Possible Solutions

1) DAP + Aweber (most expensive, most reliable)

2) DAP + 3rd party SMTP service provider (Fusemail.com or SMTP.com) (less expensive than Aweber, slightly less reliable too)

3) DAP + Good web host (cheapest, can have mixed results – all depends on your host).

You could always use DAP and external SMTP service provider like Fusemail.com or SMTP.com to send out bulk mail through DAP while totally bypassing your web host’s email system. This is probably the next best thing to using a service like Aweber.

And if you can’t afford even that, then simply use DAP on a good web host. We ourselves use just DAP and Dreamhost’s email servers to send out emails to all of our users.

And DAP also has built-in job queues to schedule outgoing emails while also making sure that you don’t exceed your web host’s hourly email sending limits (dreamhost’s limit is 300 emails/hour, I think). We use multiple SMTP servers from our own other web sites, all combined to be able to send a few thousand emails per hour.

But even with a lot of planning, it is easy to go over the hourly limit.

So the next time you see in your Job Queue that emails were sent out successfully, but the recipient never received it, here are some things to check:

1) It landed in your recipient’s junk/spam folder. Ask them to whitelist or add your email address to their contacts list.

2) You have overshot the limit, so you would have to actually send out the email again.

3) Try to send out broadcasts during a low-traffic time – say like later in the night – when you’re not actively sending out emails, and using up precious email counts from that hourly quota.

There are a few different reasons why this may not be working.

1. Cron Not Running

The DAP email-processing cron that processes the 1SC emails is not running. Check your webhost control panel -> Cron job settings. Make sure dap-emailorder.php is setup to run once every 10 minutes.

2. No Notification Emails from 1SC

The DAP cron is running but 1SC payment notification emails are not reaching your mail server. Check the email account where you expect to receive your 1SC payment notification emails and see if the order notification email from 1SC is in that mail box.

3. Incorrect Mail Server Settings

The cron is running and the 1SC order notification email is reaching your mail server – but you did not configure the mail server settings correctly in DAP Dashboard -> Setup -> Config -> Payment Processing.

Email Server Where Order Emails Come In
Email Server User Name
Email Server Password

4.”Read” Or Deleted Emails

DAP only processes order notification emails that are in the “Unread” status, to prevent previously processed emails and other non-DAP emails from being repeatedly processed.

Also, if you “pop” off the emails from that mail box (means, your email client like Outlook or Thunderbird or Gmail is “removing” your emails from the server when it retrieves them), it means that when DAP logs in to that billing email address, there are no emails there to be processed – the mailbox is empty, or the 1SC payment notification emails have somehow gotten deleted from that mailbox.

So it is possible that DAP is able to connect to your email server, but DAP is not finding any “unread” emails. Please login to your email server and mark all the payment emails that you want DAP to process… as “unread”. And also make sure that your email client does not remove the emails from that mail box.

5.Product Name Mismatch

There might be a “Product Name” mismatch. The product name has to be EXACTLY the same (including case, spaces, etc) in both DAP as well as in 1ShoppingCart. So if you have created a product by name “Widget A”, make sure your 1shoppingcart product also has the exact same name “Widget A”.

If everything is setup correctly, DAP cron will run every 10 minutes and try to process all 1SC emails.

The next time the DAP cron will run (every 10 minutes), it will pick up all the unread payment emails from 1SC.

6. Empty “Thankyou-Email Body/Subject”

Welcome email is not getting sent.

Select the product, and make sure there is some text in the “Thankyou-Email Subject” and “Thankyou-Email Body”. Whatever is in these fields is what gets sent immediately after someone purchases that product (or right after you give them access from the backend).

Now go to DAP Dashboard -> Users -> Add .

Select the product and manually add user. Now see if the thankyou email gets sent to that email id. If it got sent, then your product setup is correct.

Also check the DAP Dashboard -> Orders . Search for all orders, look up the order for the particular user in question by email.

Check the payment status and make sure there is no error there.

If you did all this and things are still not working, please do this:

1. Set DAP Dashboard > Setup Config -> Basic > Log Level = 5
2. Re-run the 1SC test purchase
3. Check the DAP Logs (DAP Dashboard > System > Logs) and send us the log text in there for troubleshooting by pasting it into a new support ticket.

7. Sending Email & Password To Buyer

Make sure you have set the thank-you message with the right merge tags for Email and Password.

8. Manually Running Cron

First set DAP Dashboard > Settings > Config > Log Level = 5

If you feel that the orders were not processed in dap, then just login to the 1SC email account where the sales/payment notification emails are sitting, and mark those orders/emails as UNREAD that you want dap to process.

Then manually run the cron script dap-emailorder.php cron by visiting the following link in the browser.

http://www.yoursite.com/dap/dap-emailorder.php

Replace yoursite.com with the name of your site.

It will just display an empty screen when complete.

Then check “Users > Manage” to see if user has been created.

- Veena Prashanth

So, let’s say you have say 3 membership levels: Silver, Gold and Platinum.

“Gold” will have all the content that “Silver” has, plus some more.

“Platinum” will probably have everything from “Gold”, plus some more.

So the way you could save time setting up all these 3 levels, is to either start with the lowest level, or the highest level.

Let’s say you start with the lowest level, “Silver”.

So create the “Silver” product fully, set up all the content dripping, email dripping etc.

And then once you’re done, while still editing the “Silver” product, click on the “Save as New” button (next to the “Save” button on the Product page).

That will create an exact duplicate of the “Silver” product – with all of its settings, content dripping and email dripping intact. And this copy will be called “Silver Copy” (just the text Copy added to the end). And this new copy will already be selected for you.

Now rename this new product from “Silver Copy” to “Gold”, save it, and then continue to add more content to it.

Then, finally, when “Gold” is fully ready, again do a “Save As New”, which would create a “Gold Copy” product.

Rename the “Gold Copy” product to “Platinum”, save it, and continue to add more content and emails to it.

Get the drift?

NOTE: On the flip site, you could also start by creating the “Platinum” product first, and then keep doing a “Save As New” and continue stripping out content to create the lower membership levels.

1. Remove the “ThankYou-Email Subject” and “ThankYou-Email Body” from the Product into which you wish to import users. Save it in a text file for later, and save the Product.

2. Go ahead and do the bulk-add of users from “Users > Add > Bulk-Add Multiple Users To A Product”.

3. Wait for the DAP Hourly Cron to run and finish importing all users. Since the “ThankYou-Email Subject” and “ThankYou-Email Body” of the Product is empty at the time of import, DAP won’t send out those emails.

4. Once all the users have been imported, put back the “ThankYou-Email Subject” and “ThankYou-Email Body” text content, and save the Product.

OPTIONAL

5. At a later point, if you want, you can send out an Autoresponder email or a Broadcast email with the merge codes for the email and password, if you want the newly imported users to get their passwords.