So once you protect a page or post in DAP, you can make it either completely disappear from your feed (for all users, members and non-members alike), or you can show partial text (by turning on sneak-peek), but in that case you must make sure you have a “more” tag entered into each of your posts.

So if your blog post is showing in its entirety, then….

1) You may not have protected the post in DAP at all, so it’s an unprotected post, which will (and should) show up in your feed

2) Or, you have turned on Sneak-Peek and haven’t inserted the WordPress “more” tag (<!–more–>) into each of your posts. If you turn on Sneak-peek, then you must insert more tags into all posts.

Also, if you have turned on Sneak-Peek, then you must also do this…

Go to “Settings > Reading” in WP admin, then set “For each article in a feed, show” to “Summary”.

If it is set to “Full text”, then it will show the full text in the feed, which is not what you want.

Here’s how to troubleshoot.

What are your sync options in DAP Admin -> Setup -> Config  -> WordPress Related Section?

Do you allow all users to be sync’d or just paid users?
Do you allow users to be synced only when they pick a username?

If you allow all users to be sync’d and do not want to force your users to pick a username before dap syncs to WP, then use these settings:

Sync DAP User Data to WordPress “Y”
Sync Paid Users Only “N”
Sync Only if Username Exists in DAP “N”

To test:
1) Add a user manually to DAP via dap admin panel
2) Note down the user’s dap login id/password
3) Open a new browser where you are not logged in to DAP as admin
4) Now login to DAP again but this time as the user you created in step 1.
5) Now visit any part of your blog. DAP will now sync user to WP.
6) Login to WP admin panel. Click on Users in the left sidebar and see if the new user was created.

This basically allows you to do partial content protection.

So if you had a blog post or page with 3 paragraphs of text and a video, you can protect just the video from certain groups of viewers, and leave the text portions open for anyone to read.

It’s a “Teaser On Steroids“.

This may be used to quickly protect content that you don’t necessarily wish to create a DAP Product for, just for the sake of protecting it.

So if you don’t care about dripping some content, but just wish to protect it from say, non-members, or make it available only to certain “levels”, then you can do it by using the DAP Shortcode, and not have to worry about adding it to any particular level first.

These Shortcodes may or may not be used within content that is already protected as part of a DAP Product. Totally up to you.

Basic DAP Shortcode

[DAP]…private content…[/DAP]

This is the shortest version of the DAP Shortcode. In this version, anything you put between the [DAP] and [/DAP] tags, will be viewable only by a logged-in user.

No other restrictions for the content to be viewed, except that the viewer has to be logged in to your membership site (via DAP). So basically all free and paid members, regardless of which product they have access to, regardless of whether their product access is active or expired, can view the private content.

Full DAP Shortcode

[DAP isPaidUser="Y" hasAccessTo="1,2,3" errMsgTemplate="SHORT"]…private…[/DAP]

This is the full version of the DAP Shortcode. All inner tags – isPaidUser , hasAccessTo and errMsgTemplate – are all OPTIONAL.

isPaidUser: Can be “Y” or “N”. NOT mandatory and may be completely skipped. If skipped, then default is “N”. So DAP ignores whether user is free or paid – which means ALL users regardless of payment status.

hasAccessTo: Comma-separated list of one or more Product Id’s that you want the user to have access to before they can view the content. So if you enter 3 different product id’s (like hasAccessTo=”2,7,14″) it means “Anyone with access to AT LEAST ONE of those products with the product Id’s 2, 17 or 14. It does NOT mean they have to have access to all of them at once. Access to any one is fine.

errMsgTemplate: This determines the HTML/text of the error message displayed, if user DOES NOT have access to the content being protected.

Values may be Can be SHORT, LONG or “” (empty). NOT mandatory. If omitted entirely from the tag, then the default template used is SHORT.

If you want no error message to be displayed, and want the protected content to silently disappear completely if user does not have access to it, then include the tag, but set it to “” (blank/empty), like this…

[DAP errMsgTemplate=""]…private…[/DAP]

The HTML/text displayed by the SHORT and LONG templates can be configured via the Setup > Templates screen, as shown below.

Examples

[DAP]…private content…[/DAP]

Viewable by Any Logged-in User

[DAP isPaidUser="Y"]…private…[/DAP]

Viewable by ANY logged in user who is also a PAID user of ANY product. Use SHORT error template by default as none is specified.

[DAP isPaidUser="Y" hasAccessTo="1" errMsgTemplate="SHORT"]…private…[/DAP]

Viewable by ANY logged in user who is also a PAID user of the product with the ID “1″ (you can get the Product id from the “Products > Manage” screen). Display HTML/text from the SHORT template if user does not have access to the private content.

[DAP isPaidUser="N" hasAccessTo="1,2,3" errMsgTemplate="LONG"]…private…[/DAP]

Viewable by ANY logged in user (FREE or PAID – doesn’t matter) who has access to EITHER of the Products – 1, 2 or 3. Display HTML/text from the LONG template if user does not have access to the private content.

Member-Specific Content

“For Your Eyes Only”
Let’s say you run a coaching program. You have 10 clients. You want Joe Customer to see a tailor-made custom video meant only for Joe, and Jill Member to see a specific PDF report written specifically for Jill’s business. Now using the new “userId” parameter in the DAP shortcode, you can now protect a piece of content so that only a specific DAP user can see it.

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

In-Page Dripping

DAP Shortcodes now include the ability to specify a “Day” right within the shortcode itself. So you can now publish, say, 10 videos on one page, and you can enclose each video’s embed code with a separate DAP Shortcode that has a different “Day” setting, so the very same page will show 1 video on Day 1, 2 videos on Day 2, 3 videos on Day 3, and so on.

Like this…

[DAP day="1" hasAccessTo="1"]Video 1 Embed Code[/DAP]

[DAP day="2" hasAccessTo="1"]Video 2 Embed Code[/DAP]

[DAP day="3" hasAccessTo="1"]Video 3 Embed Code[/DAP]

NOTE: Please remember that you may not omit the hasAccessTo field – you must use the hasAccessTo field to specify a product id, because all start “days” for a user are associated with a product.

Hiding Content From Logged-In Members

Starting DAP v4.1, you can now mark content such that it will NOT be displayed to members who ARE logged in. To put it another way, it will HIDE content from members, and show it ONLY to NON-Members.

For example, this could be your sales copy or your buy-button, that you don’t want your logged in members (who may have already purchased the product) to see.

Here’s the shortcode for that.

[DAP isLoggedIn="N"]….content to show only to NON-members… [/DAP]

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.

And then you want your actual blog content (where all of your posts show in reverse order), on a different page – like “Members” or “Lessons” or “Blog”.

Here’s how  you do it.

1. Create Static WordPress “Page”

Create a WordPress “page” that will become your blog’s new “static” home page. Let’s give it the title, “Home”. Publish your content within this WP page, and it could even have a sign-up form, or your “Buy” button(s). Publish it.

2. Create “Placeholder” WordPress page for your blog posts

Next, you create a new page which will not have any content, but will serve as a “placeholder” for all of your blog posts to be displayed in reverse chronological order, just like it would show up on any regular blog. In the example below, the page title is “Chapters”. You could call it “Lessons”, “Blog”, “Blog Posts”, “Member Blog”, etc.

3. Change WordPress Settings

In your WP Admin dashboard, go to “Settings > Reading”

a) Change “Front page displays” to “A static page“, as shown below.

b) In the drop down below…

For “Front Page“, pick the page you created in Step 1 above (your static “Home” page).

For “Posts Page“, pick the page you created in Step 2 above (your “Chapters” page).

That’s it.

To see a working example of a “static” home page in wordpress, which can be used as your Sales page or as a Squeeze page, see http://NBLEB.com/blog/

Oh, and none of this has anything to do with DAP, by the way. This is all WordPress.

There is a file in the following folder…

/wp-content/plugins/DAP-WP-LiveLinks/

by name…

DAP-WP-LoginForm-LoginLogout.html

Make a copy of that file on your desktop, rename it to…

customDAP-WP-LoginForm-LoginLogout.html

(just added the text “custom” at the front of the original file’s name).

You can then modify this new file however you want, including altering spacing, and that’s what will be displayed.

Just be careful what you change – do not modify the field names or the submit URL. Feel free to change other visual elements.

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 also integrates with vBulletin.

This post is primarily about integration with WP-based forums. For vB integration details, click here.

Integration with bbPress, Simple:Press, WP Forum, 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”.

%%LOGIN_FORM%%

This is better suited for a WP “page”. This text will be replaced by a login form using which your members can log in to your membership site.

%%AFFDETAILS%%

This will be replaced by the entire Affiliate section from the default home page at YourSite.com/dap/ . Better suited for a Page.

%%USERPROFILE%%

This will be replaced by the user profile from the default home page at YourSite.com/dap/. Better suited for a Page.

%%USERLINKS%%

This will be replaced by the user links section (the list of what products and what links user currently has access to) from the default home page at YourSite.com/dap/. Better suited for a Page.

%%FIRST_NAME%%

This will be replaced by the first-name of the user.

%%EMAIL%%

This will be replaced by the email id of the user.

%%AFF_LINK%%

This will be replaced by the raw affiliate link of the member. If you want it to show up as a link in your blog post, use it like this:

<a href=”%%AFF_LINK%%”>%%AFF_LINK%%</a>

%%MSG%%

1) Create a WP “page” with the slug “error”, and it can be accessed at http://YourSite.com/error/

2) In the body of the page, put the text %%MSG%% – followed by whatever copy you want.

3) Enter the URL from Step #1 on your “Products” page, in the field “Error Page URL”

4) Logout of DAP, and log back in for the changes to take effect.

Impact: When someone tries to visit a link that has expired, or a link that they don’t have access to, they will be redirected to the above URL, and the system error message will be shown where you put in the merge code %%MSG%%.

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

Replaces merge tag with Product-specific details (including links available to the member as part of that Product) on a specific WordPress page/post.

Log in as WP admin, and look under “Appearance > Widgets”.

You’ll see the widget. Drag this widget on to any customizable part of your theme.

The widget puts the DAP login form right on your sidebar.

When a user is not logged in, they will see the login form.

When they are logged in, they just see a “Logout” button.