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.

Use two different browsers for testing. Not two different browser tabs, but 2 completely different browsers – like Chrome and FireFox, or FireFox and Internet Explorer. Log in as DAP admin using one browser, and then as a regular user in another browser. That way, you keep the access separate, and your testing will be clean and easy.

If you are using, say, Firefox, you are logged in to DAP admin, and are browsing your blog or trying to access content on your blog, then you will only have access to the content that the admin user has access to. You, as the DAP Admin, DO NOT have automatic access to every product by default. You will have to manually give yourself access to every product you create. And if you want yourself to have “PAID” access, then you have to mark yourself as “PAID”.

That is because, if DAP gave you automatic access to all products, then you will go ahead and protect a blog post, try to access that blog post, and DAP will give you access to that content because you as admin have automatic access to the product. And then you will wonder “Hey, I protected a blog post, but I’m still seeing it.

I have protected a blog post as part of a Product. But I can still access it.

Short Answer: If you have protected a post/page/file, try to access it, and are able to do it, then it means you DO have access to it. Now let’s troubleshoot so that you understand the “how” and the “why”.

• Have you added the blog post to a Product? If you don’t add it to a DAP Product, the post/page/file won’t be protected.
• Who are you logged in as? As DAP Admin? Or as a regular member?
• Now if you search for this user by email id or last name on the “Users > Manage” page, you will see that the user does have access to the product to which the post belongs

Are you already logged in a a user who has access to that link? Maybe logged in as DAP Admin, and that is why you are able to access the link? If so, either log out of DAP, or visit your blog in a completely new browser (if you’re logged in as DAP Admin in FireFox, then visit your blog using Internet Explorer).

I have protected a blog post as part of a Product. User has access to it, but still can’t access it.

Short Answer: If you have protected a post/page/file, try to access it, and are able to do it, then it means you DO NOT have access to it. Now let’s troubleshoot so that you understand the “how” and the “why”.

• Who are you logged in as? As DAP Admin? Or as a regular member?
• Whoever you are logged in as, make sure that user (admin user or regular user) has access to the product to which the post belongs
• Have you added the post as a “PAID” or as “FREE”?
• If you have marked the post as “PAID”, make sure the user also is a “PAID” user (either there must have been a real transaction, or you must have manually marked him as “PAID”). Because free users cannot access content that has been marked as “PAID”.
• Maybe the user’s access to the product has expired. Check the user’s “Access Start Date” and “Access End Date” for that product. The start date should be current (not be in the future) and the end date should be current (shouldn’t be in the past, which means his access to the product has expired)

I don’t want the links to all my protected blog posts showing up on my blog’s home page

Make sure you have “Sneak-Peek” turned off in the DAP Admin Config section. Once you do that, posts that are protected will not be displayed on the home page as well as if someone tried to visit the link directly.

Why do I see the “Lock” symbol on my blog’s home page?

It’s possible that you have no published posts (it’s a new blog), or you have probably protected all of the posts by adding them all to a DAP Product.

1) Open the file error.php that is stored in the /dap/inc/ folder.

2) RENAME it as (or COPY it as) customerror.php.

3) You can put ANY kind of HTML content within this. Images, javascript, css,, buttons, text, whatever. Any HTML can be used in this file.

4) Upload this new file customerror.php back to same folder /dap/inc/

5) error.php doesn’t matter any more. Whether you delete it, or just leave it alone, the fact that there is a customerror.php file in the same directory means that DAP won’t even bother about error.php any more.

6) Future updates of DAP will not touch your customerror.php file. So updates or upgrades will not mess with your custom error page copy.

The fastest way to protect files is to upload them to your wordpress blog when you are writing a new post. All such files will be stored in a folder called “wp-content/uploads/….”.

Alternatively, you could also upload files directly using FTP, to the “wp-content/uploads/” folder and DAP is configured right off-the-shelf to protect any file inside the “wp-content/uploads/” folder.

B) Protecting Regular Web Site Files Outside of WordPress

1. Go to the following directory within the “dap” folder on your desktop:

dap > client > website

2. Open the .htaccess file in this folder.

3. In your web site’s root folder (where you have your home page – index.php or index.html)…

i) if you already have an existing .htaccess file., then open it and COPY the text from Step 2 above and PASTE it at the very end of this file.

ii) If there is no .htaccess in your root folder, then simply copy the file from Step 2 to your web site’s root folder.

That’s it.

TESTING:
Now add the link to your non-wordpress file to DAP from the DAP Admin Control Panel.

Then, open a different browser (not different window – a totally different browser – like, if you’re logged in as DAP admin in FireFox, open IE)  and try to access your file directly and see if DAP redirects you to the login screen.

If not, take a deep breath – it’s NOT DAP

It’s just that you missed something (or screwed something up .

Revisit the steps above, and if you still can’t figure it out, you might want to think about uploading the file to wordpress (see Section A above) .

But if you’d rather get this working, then just open a support ticket, and we’re standing by to help you

That’s it!

But if you want to put this form “within” your WordPress blog, so as to give your login form the same Look & Feel as the rest of your blog, all you need to do, is…

1) Create a WordPress “Page” (not ‘post’) with the text %%LOGIN_FORM%% in the body of the page, and a title of say, Login, and save the new page. If you used the text “Login” for the title, then the actual link to this page would be YourSite.com/blog/login

2) This page now shows up as “Login” along with the rest of your “pages” on your blog.

3) Go to DAP Admin > Config > Advanced (drop down). Scroll down to the field that says:

Location of your login page (eg., if using WordPress). Should start with a forward slash (`/`)

In the text box, enter the link to the login page from Step 1, minus the domain name. So, it would look like:

/blog/login

That’s it!

When someone clicks on the “Login” link, or tries to access a post that they are not authorized to, the user is redirected to the login page.

Related: Where is the Logout Link?

That means, if you read this post and don’t understand a word, then this is NOT for you.

For this to work, you must have already installed DAP WP LiveLinks.

Now, when someone comes to your wordpress blog, assuming you have already activated DAP LiveLinks, then none of the posts you have protected will even show up on the home page, or will show up if someone tries to visit them directly (say, from a bookmark or link in an email). Which means, as far as your visitor is concerned, those posts don’t even exist in your blog.

Now as powerful as this plugin is, from an SEO perspective, if your visitor (who is not a member, and one who is not logged in) can’t even see the post, then neither can Google. This means, if you do a blog-and-ping, when Google arrives at the permalink of your new post, because the post is protected, DAP will redirect Google to your login page. This means, you don’ get the benefit of SEO for your new post.

Also, from a “Curiosity” standpoint, if you protect all of the posts, then your visitor will only see a handful of non-protected blog posts.

So, giving them a “sneak-peek” of the post your home page as well as on the permalink, is a great way to get them excited about your content.

How to turn on Sneak-Peek

Go to DAP Admin > Config > WordPress Sneak-Peek

It is set to “N” (no) by default. Change this to “Y” and click on the “Update” button to save the change.

And then when they click on the “more” button to read the rest of the post, the full post is protected anyway, and they are presented with a login screen.

WARNING: VERY IMPORTANT IF YOU TURN ON SNEAK-PEEK

As soon as you turn on Sneak-Peek, DAP will show all content from your blog posts, but only up to the “More” tag. This means, if you don’t have a “More” tag in any of your content, then all of your blog posts will show to all users, regardless of whether they have access or not.

So, the most important thing here is this:

SNEAK-PEEK and MORE are INSEPARABLE.

If you do sneak-peek, you MUST include a “More” tag.

So when you create a WordPress blog post, split the post into two parts using the “More” tag. This creates a “public preview” portion of the actual post, that shows up on your blog’s home page and in the permalink when that post is displayed. To read the rest of the post, your visitor has to click on the “More” link, and that’s when depending on whether the user has access, the rest of the post will be displayed.

1. Log in to DAP Dashboard and go to the “Products/Lists” page.
2. Select the product to which you want this blog post to be a part of
3. Scroll down to the “ContentResponder” section
4. On the left, you will see a list of blog posts & pages that have been published
5. Select one or more (hold Ctrl + Click to select multiple)
6. Click on “Add Selected Posts/Pages” to protect the posts/pages.
7. It will now show up on the right-hand side of the box.
8. Click on “Edit” next to the link to configure dripping.

How do I protect a file?

Use the “File Browser” on the “Products/Lists” page to browse through a folder on your web site, and next to each file, you will see an “Add” link. Clicking on that link will add that file to the product.

I have protected a blog post. But I can still view it without logging in.

1. Are you already logged in a a user who has access to that link? Maybe logged in as DAP Admin, and that is why you are able to access the link? If so, either log out of DAP, or visit your blog in a completely new browser (if you’re logged in as DAP Admin in FireFox, then visit your blog using Internet Explorer).

2. After you set up DAP, did you visit the “Permalinks” section and click on the “Save” button at least once (even if you didn’t make any changes to your permalinks structure)?

3. Have you added the blog post to a Product? If you don’t add it to a DAP Product, the post or file won’t be protected.

Can I protect an entire category of posts at one go?

Yes, absolutely!

See Protecting An Entire WordPress Category.

Why do I see all of the protected posts on my blog’s home page? (OR) I don’t want the links to all my blog posts showing up on my blog

Make sure you have “Sneak-Peek” turned off in the DAP Admin Config section. Once you do that, posts that are protected will not be displayed on the home page as well as if someone tried to visit the link directly.