Entries Tagged 'Config' ↓
September 2nd, 2010 — Access Control, Config, Examples, Protecting Content, Setup, Users
Creating 1 Single Login & Password For All Users
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:
- Most important: Go to Setup > Config > Advanced > “Max. # of User Logins From Different IP`s” and set it to a very high number – like 99999999. You’ll need to do this because everyone will be logging in using the same email/password, and you don’t want DAP to lock out the public account (you’re about to create below).
- Create a “public” user manually, with an email id like, say, “demo@yoursite.com” . DAP will assign a random password to the user (unless of course you have set the “Default” password in Config).
- Change this password also to something public – like ‘demo’
- Then if you don’t care about collecting anyone’s email id, then you could publish this info publicly on your web site
- But if you wish to collect people’s email id’s, and *then* give them this public email/password, then you can still sign them up using the “Direct Signup Form”. And in the welcome email, instead of sending them their own email id and password, send them the public email id and password.
August 24th, 2010 — Access Control, Config, Customization, LiveLinks, Protecting Content, Protection FAQ, Setup, WordPress
DAP has a feature called “Sneak-Peek” where you can show a part of your blog post for all casual visitors, 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.
How this works
WordPress has a feature called the “more” tag. Basically it is a piece of text that you insert into your posts or pages (it actually looks like this: <!–more–>) and then WP will 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 that looks like two rectangles, on the WP Publish page.
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 WP theme.
So regardless of what it says, when you have a protected post, by default 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, and in the DAP Dashboard, go t…
“Setup > Config > Advanced > WordPress Sneak Peek: Show snippets of post (upto the `More` break) even for protected posts?”
… and set the above setting to “Y” (for ‘yes’), then on your blog’s summary page (which lists all of your posts), all posts with the more tag (protected and un-protected will anyway show up to the more tag, but 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, will show her the rest of the post. And if the user is either not logged in, or 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.
August 23rd, 2010 — Access Control, Config, Customization, Products, Setup, Troubleshooting
“Logged-in URL” on Product page is not taking user to right page after log in.
The Logged-In URL field will work only if user has access to just that one product. If user has access to more than 1-product, DAP cannot decide which Product’s “Logged-In URL” to redirect the user to. So it simply uses the “Global” logged-in URL in “Setup > Config > URL to which User is redirected to, right after log in.”
So if you’re testing the “Logged-In URL” field, make sure you create a test user with access to just that one product, and then log in as her and test.
August 16th, 2010 — Admin, Affiliates, ClickBank, Config, Customization, Merge Tags, Setup
There are many reasons for wanting to do this.
1) You simply don’t wish to let people know that you have an affiliate program – maybe it is so that you don’t want to confuse the mom-and-pop niche that you are in with crazy words like “Affiliate” and “Commission”
2) You deliberately want to disable certain users from using the affiliate link, and not award them any commissions, even though they know what that link is.
3) You are using a 3rd party affiliate service – like ClickBank – and don’t want to use DAP’s built-in affiliate program.
At this time, you cannot really do (2). There is no way to stop DAP from tracking an affiliate’s referrals and not tracking their earnings. Only work-around right now, is to simply not pay them at all, for whatever reason (you better have a very good reason, if not it could be legal trouble for you).
Here’s how you can do (1) – which essentially works for (3) also.
A) If you are using the default dap/index.php as your members’ home page, then all you have to do is to go to…
Setup > Config > Advanced > “Should Affiliate Section be displayed on User `Home` Page? (If using ClickBank, set this to `N`)”
And set it to “N” (for “No”).
That will essentially “hide” the affiliate section from showing up on the default DAP home page.
B) If you are not using the default dap/index.php, and are putting all of the DAP member content (like User Profile, User Links, Affiliate Details) etc right into your WordPress blog, then just skip the Affiliate Details part, and don’t create a custom page for Affiliates within your blog. If you don’t create the page, then they won’t see it, that’s all.
NOTE: If you don’t want anyone to get any commissions, also make sure that you don’t set up any commissions on the “Affiliates > Set Commissions” page.
So basically, in both (A) and (B), you are essentially “hiding” the affiliate program details, and not really disabling it.
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.
August 15th, 2010 — 3rd Party Integration, 3rd Party List Integration, Aweber, Config, Email, Examples, Features, Merge Tags, Personalization, Setup, Users
Starting DAP 3.8, DAP has a new feature where you can ask DAP to always generate a pre-chosen, default password of your choice for all new members.
So all new users will be assigned the same default password, which they can of course change as soon as (or any time after) they login.
This is especially helpful for new users, if instead of DAP, you want a third-party service like Aweber 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 > Advanced > “If you want DAP to generate a default password for all new users, enter it here. If not, leave blank”
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:
Hello {!firstname},
Welcome to Example.com. You may log in to your member’s area at:
Email: {!email}
Password: changethis
Thank you,
- 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.
July 9th, 2010 — Access Control, Config, Customization, Examples, Products, Setup
Starting DAP v3.8, we have a new feature called “Product-Specific Details“.
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.
June 22nd, 2010 — 1ShoppingCart, 3rd Party Integration, ClickBank, Config, Cron, Errors, FAQ, Integration with Shopping Carts, Payment Integration, Payment Setup and Integration FAQ, Products, Setup, Transactions, Troubleshooting, Users
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
May 24th, 2010 — Bulk Email, Config, Customization, Email, Email Resources, Personalization, Setup
Here are the merge-tags that you can use in outgoing autoresponder and broadcast emails sent through DAP. (Click here for merge tags you can use in your WordPress blog posts/pages)
%%FIRST_NAME%%
This will be replaced by the first-name of the user.
%%LAST_NAME%%
This will be replaced by the first-name of the user.
%%EMAIL%%
This will be replaced by the email id of the user.
%%PASSWORD%%
This will be replaced by the password of the user.
%%SITE_NAME%%
This will be replaced by whatever text you have entered in “Setup > Config > Basic > Site Name” in your DAP Dashboard.
%%ADMIN_NAME%%
This will be replaced by whatever text you have entered in “Setup > Config > Basic > Admin Name” in your DAP Dashboard.
%%ADMIN_EMAIL%%
This will be replaced by whatever text you have entered in “Setup > Config > Basic > Admin Email” in your DAP Dashboard.
%%AFF_LINK%%
This will be replaced by the actual affiliate link of the member (Eg., http://yoursite.com/dap/a/?a=1234)
%%SITE_URL_DAP%%
Replaced by your actual web site url (Eg., http://yoursite.com)
%%UNSUB_LINK%%
This is replaced by a 1-click Unsubscribe link that you can add to the bottom of your outgoing broadcast and autoresponder emails.
This will be replaced by whatever text you have entered in “Setup > Config > Basic > Admin Email” in your DAP Dashboard.
May 4th, 2010 — 3rd Party Integration, Access Control, Admin, Config, Customization, DAP, Database, LiveLinks, Setup, Users, WordPress, WordPress FAQ
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:
- For the sync to work, you must first setup and save the above 2 config settings
- 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.
- Your user must log in through a DAP login form (not the WP login form).
- 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.
- 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.
- 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
February 27th, 2010 — 3rd Party Integration, Access Control, Config, Forums, Setup, Users, WordPress, WordPress Plugins
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.
- Download the 3rd party wordpress forum plugin
- Install it as per their instructions. We don’t support the installation or setup of the forum plugin itself.
- Log in to your DAP Admin Dashboard and click on “Config > Advanced”.
- 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.)
- 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”.