DAP allows you to import users in bulk from an external system or database.

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.

The Basics Of Sending Email Through Your Web Site

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.

The same troubleshooting steps apply for both 1ShoppingCart & ClickBank integration.

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

There are many ways in which you can protect videos.

Case 1: The video file is stored on your web site

By default, DAP can only protect files that are stored on the same web site where DAP is installed.

So if you install DAP on YourSite.com , then your files must also be located on YourSite.com. DAP installed on YourSite.com cannot protect files (.mp4, .mp3, .html, .pdf, .doc) that are stored on AnotherSite.com.

So assuming the files are stored on the same site as DAP, you can (and should) protect both the actual video file, as well as the blog post or page in which the embed-code for your video is published, by adding both to a Product.

This gives you 2 levels of protection for your videos:

Level 1: The blog post or page containing the video player code, itself is accessible only by authorized members.
Level 2: When an authorized user gets legitimate access to the page where the video is published (because they’re a paying member, say), even if they try to do a view source and figure out the location of the video (eg., http://yoursite.com/videos/howtovideo1.mp4) , and pass it around by email to their friends (or post the link in an online forum), their friends still can’t view the video, because the video link itself is protected by DAP.

If you have some text that you want the casual visitor (and Google) to read, but wish to protect only the video, then you could turn Sneak-Peek on (in Setup > Config > Advanced), insert a WordPress more tag (<!–more–>) into your post just where you want the content to start being protected, and put the video player’s embed code after the more tag.

Case 2: Video file is stored on Amazon S3

The only 3rd-party-stored video files that DAP can protect at this time are videos (and other files) that are stored on Amazon S3. DAP cannot do this by itself, but uses a special WordPress plugin called S3MediaVault.com , which is a plugin we developed specifically to make Amazon S3 videos play in your WordPress blog posts/pages. So again you get 2 levels of protection for your videos…

Level 1: DAP protects the post/page where the special S3MV video player code is embedded
Level 2: The S3MediaVault plugin makes sure that even if someone tried to do a view source and figure out the actual link to your Amazon S3 video, they still won’t be able to view the video.

WARNING: Video stored on other 3rd party video sites

DAP cannot protect, say, videos that are embedded from other 3rd party web sites like YouTube or Hulu. Of course, DAP can always protect the blog post or page itself that contains the video, but once an authorized user gets valid access to that blog page, they can see that it is a YouTube video (say), and then pass that YouTube video link to their friends, in which case DAP cannot protect that external YouTube video link.

(Or… “DAP vs MailChimp”, “DAP vs. GetResponse”, …. “DAP vs 3rd-Party-List-Service”)

We often get asked why use Aweber (or other third-party list service) when DAP itself is an autoresponder.

So here’s a brief overview of when and why it makes sense to use DAP or Aweber.

Why Aweber

DAP is not an email service like Aweber.

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

If your inexpensive shared web host is hosting a large number of sites on one server, and one of them sends out spam (or mistakenly gets flagged for spam), that will put the email deliverability of every web site on that servver, 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.

Your customers never get your email. Your campaign suffers. Your conversion plunges.

This won’t happen with Aweber.

Aweber (and other premier email service providers) have staff on hand, spend a lot of time, money and resources dealing with regular ISP’s (like AOL and SBC) to make sure their lists – and their reputation – remain clean.

Which is probably why they shut down large lists without much of a warning to you, and do other similar crazy stuff. I guess it works for them – and the other Aweber users, because when you send out an email through your Aweber list, it almost always gets there in your recipient’s inbox.

Which is very cool. Which is why they also charge so much for their service.

But if you can’t afford their high fees, then you can of course use DAP’s built-in email autoresponder, whose deliverability is only as good as your host’s spam reputation

Of course, you can 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 Aweber only.

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.

So given a choice, here are your email options in the exact order listed.

1) DAP + Aweber: Match made in heaven

2) DAP + 3rd Party List Services: 2nd best option

3) DAP + Your Web Host: Very usable and workable option as long as you are hosting with a decent host.

Feel free to comment below if you have any questions.

NOTE: This content is for advanced users only, who understand the concept of user tables, database, etc. If you don’t understand any of this, then just ignore this – you don’t really need to know this in order to use DAP. This is only an explanation for those who wish to go under the hood of DAP and its integration with WordPress.

As you probably already know, WordPress has its own user database.

DAP has its own User database, and doesn’t use the WordPress database – for many reasons, not limited to the following…

1) Ability to store more user information than what WordPress allows

2) More powerful user search, profile updates, affiliate information, etc.

So, if you want to use any WordPress based plugins – like WordPress Forums or Subscribe2Blog – these forums are looking at WordPress’ native user database.

Now comes the necessity of “syncing” the DAP user data and your WordPress user data.

In the DAP Dashboard, in “Setup > Config > Advanced“, you will see two settings for syncing DAP & WP user data.

(1) Sync DAP User data and WP User data

If you turn this to “Y” (for “Yes”), then every time someone logs into DAP, their DAP user data (just name and email) is automatically “synced” with WordPress user data. If you set this to “N”, then no data will be transferred from DAP to WordPress.

(2) Sync WP data only for PAID users

This one matters only if you have set (1) above to “Y”.

If you want only your “PAID” members to be synced with WordPress, then set this to “Y“.

If you want both “FREE” and “PAID” members synced with WordPress, then set this to “N“.

Here’s how it actually works:

1. For the sync to work, you must first setup and save the above 2 config settings
2. After you save the above two config settings, make sure you log out of DAP and re-log in (if you are/were logged in and testing as a regular user), because only then, the Config settings above will take effect.
3. Your user must log in through a DAP login form (not the WP login form).
4. Make sure the user is redirected to any part of your WordPress blog after log in. This can be done via “Logged In URL” setting in DAP Config.
5. The user can be redirected to any WP page, WP post or even your blog home page – that’s the only time the ’syncing’ kicks in.
6. When user lands on any page/post of your WP blog, then the DAP LiveLinks plugin (which you have already installed & enabled) kicks of the “sync”, copies the logged in member’s name and email over to the WordPress user table, and also automatically logs him into your WordPress blog.

That’s all there is to it.

Also see: Forum Integration

DAP currently integrates only with WordPress-based Forums – like bbPress, Simple:Press, etc.

What this essentially achieves, is that once your forum plugin has been integrated with DAP (explained below), anyone who is a member in your DAP-powered membership site, will also be automatically be logged in to your forum when they log in to your membership site.

So they won’t have to log in twice [like, once into DAP and once into your forum].

Here’s how you set up the DAP/forum integration.

1. Download the 3rd party wordpress forum plugin
2. Install it as per their instructions. We don’t support the installation or setup of the forum plugin itself.
3. Log in to your DAP Admin Dashboard and click on “Config > Advanced”.
4. You have two settings on the page that applies to forum integration:
   “Sync DAP User data and WP User data”
   “Sync WP data only for PAID users“.(Both are explained further below.)
5. Pick “Y” or “N” for each of them, and you’re all set.

First, a quick explanation of both settings.

1) Sync DAP User data and WP User data

If you turn this to “Y” (for “Yes”), then every time someone logs into DAP, they’re automatically logged into WordPress too (with a “User” role). And because they’re logged into WordPress, that means they’re also logged into your forum (because you are using a WordPress-based Forum Plugin which already integrates with your WordPress blog.)

2) Sync WP data only for PAID users

This one matters only if you have set (1) above to “Y”.

So once you have decided to turn on the DAP/Forum plugin integration, then if you want only your “PAID” members to have access to the forum, then set this to “Y”.

If you don’t care about both FREE and PAID users accessing your forum, then set this to “N”.

So you have an email list on a 3rd party autoresponder service – like Aweber or GetResponse.

And you want everyone who joins your DAP-powered membership site, to also be automatically added to this 3rd party list, so that you can use the 3rd party service to send out autoresponder emails (instead of, or in conjunction with, DAP).

Now if your 3rd party autoresponder service provide a “subscribable” email address (like, yourlist@autoresponder.com), then all you have to do to add all DAP members to this list, is to put the above email address (yourlist@autoresponder.com) into the “3rd Party Email Notification” field on the “Products” page in DAP.

For example, click here to see how DAP can automatically add members to your Aweber list.

But some 3rd party autoresponder services – like GetResponse, say – don’t allow you to use this subscribable email address (like, yourlist@autoresponder.com) to automate the adding of new members to the list. And they also don’t have an API, that scripts like DAP can use to seamlessly add members directly on the backend.

This is where this feature of DAP comes in handy.

In the documentation below, when we say 3rdPartyForm, we are referring to the sign-up form HTML provided by your 3rd party autoresponder service (like GetResponse) that will allow someone to enter their name and email id in the form and join the list. And when we say autoresponder, we are referring to your 3rd party list service.

At a high level, here’s how this integration works…

1) You first publish this 3rdPartyForm (that has your autoresponder id and other details) to a special php page within DAP (explained below)

2) Buyer buys your product from your web site’s sales page, DAP automatically creates an account, and sends buyer the “Activation” (double-optin) email. (Note: You must set your DAP Product to be double-optin in order for this to work).

3) Buyer gets double-optin email from DAP, that says something to the effect of: “You must click on the activation link below activate your membership account and get access to the product you have just purchased”. (Note: You can customize the double-optin email text on the “Products” page).

4) When buyer clicks on the DAP “Activation” link, she is first presented with your 3rdPartyForm. This form will be already pre-filled with her name and email address, and also disabled (name and email cannot be edited)

5) Upon clicking the submit button on this 3rdPartyForm, she is first added to your autoresponder, and then her DAP account is activated.

Now here’s how you set up the 3rdPartyForm…

1. Download this zip file, and unzip the php file inside – it’s called 3rdPartyForm.php. This is just a sample file. This file will have a different name by the time you use it.

2. Open this file with a text editor. Paste your 3rdPartyForm HTML that you have gotten from your autoresponder service.

3. Your 3rdPartyForm will have a field to redirect the user to a “success” page after the user has been successfully added to the 3rd party list. It will be a field named something like “redirect”.

This is how the form field looks in Aweber’s signup forms:

<input type=”hidden” name=”redirect” value=”<?php echo Dap_Config::get(“SITE_URL_DAP”); ?>/dap/activate.php?c=<?php echo $c; ?>&p=<?php echo $p; ?>“>

Now your autoresponder service might call it “redirect”, “success_url” or something similar. Just make sure whatever the field name is, the “value” of this field is exactly the same as shown below:

Do not change the special PHP code in the value field. Only change the name of the field (redirect, in the above example) if required.

3. Now go to the DAP product whose members you want to add to your autoresponder. From the Product page, get the “Product Id” field (shown right above “Product Name”). It is a number – like “1″ or “2″ or “10″. Make a note of this Product Id.

4. Now rename the 3rdPartyForm.php to <ProductId>.php . So if the Product Id from Step 3 above was 1, then name this file as 1.php. If it was 10, then name the file as 10.php.

5. Upload this 1.php (or 10.php) file directly to the folder “/dap/inc/“.

That’s it!

Just make sure the Product for which you are doing this, has double-optin enabled – which means put some text in the Double-Optin Subject and Double-Optin Body of that product.

Try adding a new user to that product, and you should see the 3rdPartyForm being presented first when the user clicks on the activation link. And only upon the submitting of this form, the user is activated in DAP.