This is for when you don’t care about assigning unique usernames and passwords to your users, and would rather given all of your members (or site visitors) a single email id and password to log in to your membership site.
Here’s how you can do it:
DAP has a feature called “Sneak-Peek” where you can show a part of your blog post or page to casual visitors (as well as to search engines like Google) and then when they click on the “Read more…” link, the protection will kick in for the rest of the post, and DAP will say something to the effect of “Sorry, you must be logged in to access this content. Please login below or click here to get access”.
And that error page will contain both the login form, as well as a link to your sales page. Of course, you can customize this error page to say whatever you want, but that’s another topic altogether.
Sneak-Peek allows you to show “teaser” content to potential members, instead of fully locking it up and showing just an error page. Using Sneak-Peek allows you to show some content to casual visitors in order to get them to subscribe to see the rest of the content, as well as keep some content open so that search engines like Google will have some content to index in their search databases, so that the open part of the content can show up in search results for potentially matching keywords, and bring you some free organic search traffic to your site.
WordPress has a feature called the “more” tag. Basically it is a bunch of text (<!–more–>) that you insert into your posts or pages. And WP will then break up your post right at the point where you inserted the more tag, and replace that tag (and everything that follows) with a “Read more…” link
You can also insert the more tag in to your post or page, by clicking on the icon shown in the image above – that looks like two rectangles separated by a dotted line – on the WordPress page/post edit screen.
Of course, exactly what that “Read more” link will say (it could say, for eg., “Click here to read the rest of this post”) is determined by your actual WP theme.
Regardless of what it says, when you have a protected post, by default (when sneak peek is off) that post will completely disappear from your blog for non-members and those who are logged in, but don’t have access to it yet. And even to Google.
But if you insert the “More” tag in to all of your pages and posts, then on your blog’s summary page (which lists all of your posts), all posts with the more tag (protected and un-protected will show up to the more tag, and when someone clicks on the “Read more’ link, that’s when DAP’s security kicks in and if the user has access to that content, it will show her the rest of the post. But if the user is either not logged in, or is logged in and does not have access to that content (either access is yet to come because of the drip, or content has already expired), then it will show the appropriate error message.
In your DAP Admin Dashboard, go to…
“DAP Admin > Setup > Config > WordPress Sneak Peek: Show snippets of post (upto the `More` break) even for protected posts?“
… and set the above setting to “Y” (for ‘yes’),
To protect your content, if you turn on “Sneak-Peek” in DAP, and you inadvertently (or intentionally) don’t insert the “more” tag into a post, then the entire post will get hidden and protected by default, and nothing will be shown except the error message.
DAP has 3 fields which are applicable at a Product-level.
If a content (page/post) is part of just one single product, then the Product-level settings will apply.
But if a content (page/post) is part of multiple products, then DAP can’t figure out which product’s settings to use – so it falls back to the “GLOBAL” equivalent of that same setting under Setup > Config.
The 3 fields are…
All 3 of these have both a Product-level setting, plus a fall-back Global setting under Setup > Config.
If the user has access to more than 1 DAP Product, then DAP cannot decide which Product’s Post-Login URL to redirect the user to. So it simply redirects the user to the global equivalent of that URL at Setup > Config > Post-Login URL (Global)
So if you’re testing the “Post-Login URL” field, make sure you create a test user with access to just that one product, and then log in as her and test.
If the content that user is trying to access, but is not eligible to access, is part of just one DAP product, then that product’s “Error Page URL” will apply. And this field is set to “/dap/product-error.php” by default. Even if you set this to blank, it will assume that to be the same as teh default value, and the default “In-page Error Message” will apply.
If the content that user is trying to access, but is not eligible to access, is part of more than 1 DAP Product, then DAP cannot decide which Product’s “Error Page URL” to use. So it simply uses the global equivalent under Setup > Config > Error Page URL (Global)
If you want to redirect the error page URL to a custom error page, then you have to enter that into each product, as well as one for the global one.
If the content that user is trying to access, but is not eligible to access, is part of more than 1 DAP Product, then DAP cannot decide which Product’s “Sales Page URL” to show on the “In-Page Error Message” shown to the viewer. So it simply uses the global equivalent under Setup > Config > Sales Page URL (Global)
So make sure you have set up a URL in that field.
When you click on a category (instead of a single post), then because the category could contain many posts, each of which could be part of multiple Products. So DAP is unable to choose just 1 single Product from which to pick the “Error Page URL” and redirect the visitor to. So it just shows the error message with the padlock image, which can be customized. Click here for details.
There are many reasons for wanting to have more control over the affiliate program – or even completely disable it for the entire web site.
1) You simply don’t wish to let people know that you have an affiliate program – maybe it is because you don’t want to confuse the mom-and-pop niche that you are in with crazy words like “Affiliate” and “Commission” :-). Or you just don’t need affiliates and don’t wish to pay commissions
2) You want to allow only certain users to be affiliates. You don’t want every member to automatically become affiliates.
3) You are using a 3rd party affiliate service – like ClickBank – and don’t wish to use DAP’s built-in affiliate program.
This is easy to do. Don’t announce any affiliate program. Don’t say anywhere that you have one, or that you’re offering commissions. Do not setup commissions for your products. Do not create an “Affiliate Info” page, so no one will know what their affiliate link is, and since no commissions are set, no one will get paid anything.
Basically, don’t do anything to set up any of the the affiliate stuff, and that’s as good as having no affiliate program.
If you do not want all members to become affiliates, and only want people you want – like your business associates and JV partners – to be the only affiliates, then…
a) Create a separate product called Affiliates. But do not publish a public sign-up form for that product. So no one can sign-up for that, and the only way to get access to it is if you manually added them in from the DAP Admin Users > Add screen.
b) Create the Affiliate Info page that displays all of the affiliate information and stats. But add that page only to this Affiliates product, and not to any other product. So only those with access to the Affiliates product can even get to the Affiliate Info page.
If you are using DAP with a non-WordPress site, or simply using the the default http://YourSite.com/dap/index.php page as your members’ area, then all you have to do is go to…
DAP Admin > Setup > Config > Display Affiliate Details
… and set it to “N”.
That will essentially “hide” the affiliate section from showing up on the default DAP home page (at http://YourSite.com/dap/index.php)
NOTE: In a future version of DAP, we will have the ability to selectively turn off an individual’s ability to use their affiliate link, so DAP will completely ignore all referrals from the affiliate, and won’t track anything from them.
DAP has a feature where you can ask DAP to always generate a pre-determined, default password of your choice for all new members.
So all new users will be assigned the same default password, which of course, they can change as soon as (or any time after) they login.
This is especially useful if you want a third-party service like Aweber – instead of DAP – to send out the new member’s “Welcome Email” which contains their email and password.
Since DAP is unable to pass the randomly generated password to Aweber, instead, you can setup a default password by going to
Setup > Config > Default Password
This can be found under the Miscellaneous section on that page.
So if you set this password to say, changethis, then DAP will give out the same password to all new users.
Then, in the welcome email you configure at, say, Aweber, you would put the Aweber merge code for email id, and then enter this pre-selected password (because you already know what it is) into your Aweber email, like this:
Welcome to Example.com. You may log in to your member’s area at:
– Admin from Example.com
And if you ever change the default password in DAP, don’t forget to also change it in your welcome email at Aweber (or 3rd party email service).
Also, don’t use the default password in any subsequent emails, other than the Welcome email (very first email sent to member through Aweber), because the member may have already changed their password by then.
WARNING: You must have also set up DAP/Aweber integration first before you attempt to do this.
You already know that you can create a “My Content” kind of page within WordPress, that will list all products that a user has access to, and then each product will list the content that they currently have access to (content that has already dripped on them).
But this page is a full-summary of all products, all listed on one page.
Instead, if you wished to create product-specific download pages, where you create a separate page for each product, that lists all the content within just that product alone, then that’s where DAP’s “ProductLinks” Widget comes in handy.
Here’s how you set it up.
Replace the entire text <id> with the actual Product id from DAP (Products > Manage)
So, if the product’s id is 6 in DAP, then the merge code becomes:
Save the page. And if you gave the page the title “Gold Membership Content”, then the permalink for this page will be:
There are a few different reasons why this may not be working.
The DAP email-processing cron that processes the 1SC emails may not be running. Check your webhost control panel -> Cron job settings. Make sure dap-emailorder.php is setup to run once every 10 minutes.
The billing email id you have entered in DAP at Setup > Config > Payment Processing , should be entered into the “Order Notice Email – Primary Destination” field in your 1SiteAutomation/1Shoppingcart account, on the Setup > Orders > Notifications section. If by chance you enter it into the “Order Notice Email – Primary Destination” field, it WILL NOT WORK.
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.
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
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.
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.
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 -> Log Level -> Log All activity
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.
Make sure you have set the thank-you message with the right merge tags for Email and Password.
First set DAP Dashboard > setup -> Config -> Log Level -> Log All activity
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.
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
Here are the merge-tags that you can use in outgoing autoresponder and broadcast emails sent through DAP.
This will be replaced by the first-name of the user.
This will be replaced by the first-name of the user.
This will be replaced by the email id of the user.
This will be replaced by the password of the user.
This will be replaced by whatever text you have entered in “Setup > Config > Basic > Site Name” in your DAP Dashboard.
This will be replaced by whatever text you have entered in “Setup > Config > Basic > Admin Name” in your DAP Dashboard.
This will be replaced by whatever text you have entered in “Setup > Config > Basic > Admin Email” in your DAP Dashboard.
This will be replaced by the actual affiliate link of the member (Eg., http://yoursite.com/dap/a/?a=1234)
Replaced by your actual web site url (Eg., http://yoursite.com)
This is replaced by a 1-click Unsubscribe link that you can add to the bottom of your outgoing broadcast and autoresponder emails.
You can send custom field values in the DAP emails by using merge tags like this – %%custom_tax_id%%
Add ‘custom_’ in front of the custom field’s database field name.
So if you have defined a custom field called tax_id in your database, to include this field in the autoresponder/broadcast email, just add this – %%custom_tax_id%% to the body of your email.
That’s it. When the user receives the email, dap will automatically replace the merge tag with the user’s tax id value.
So if your email message body contains the following text:
Your Tax Id: %%custom_tax_id%%
When the user receives the message, it will look like this (in this example, the user’s taxId = 9999):
Your Tax Id: 9999
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.
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.
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:
That’s all there is to it.
Also see: Forum Integration
DAP currently integrates with all WordPress-based Forum plugins (some of them mentioned below) as well as two non-WP based (vB & XenForo).
So if a member logs in to your membership site via the DAP login form, then they will also automatically be logged in to your forum. That’s called “Single Sign-on” and DAP supports it with all of the above forum software.
The WordPress-based forums listed above (Simple:Press, Mingle, etc) are not really full-featured (like XenForo or vBulletin). DAP doesn’t – and cannot – protect individual forum posts or threads if you used the basic WordPress-based forums. But they’re all free, have pretty decent forum features, easy to set up and use, and will work just fine for most people.
However, if you want a more full-featured forum software that will give you greater control over many details, allow you to protect content at a thread or forum level, and want tons of user and admin features, then we highly recommend going with XenForo (XF) or vBulletin (vB). XF and vB are not free, have a slightly bigger learning curve than the simple WP forum plugins, and require more setup and maintenance overall. And if you want the best forum plugin, and are willing to pay the price (dollar-wise as well as effort-wise) and put in the time to set it up, then XF is the way to go, and DAP integrates extremely well with XF.
Now, the rest of this post is about integration of DAP with the WordPress-based forums.
(For XenForo integration details, click here)
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.
Now, a quick explanation of both settings.
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” WordPress 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 installation)
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 want both FREE and PAID users accessing your forum, then set this to “N”.