Log In As Member

Starting DAP v4.4, all passwords are encrypted. Previously, one of the main reasons that we had made it open, was because of many DAP admins asking for it to be that way so that they could log in “as” one fo their members to see what they’re seeing, for troubleshooting, etc.

But since the passwords are now encrypted, we have provided an alternate way for DAP admin to log in as a regular user/member.

Log In As Member (LIAM)

• If your primary browser is say Firefox where you’re normally logged in as WP admin and DAP admin, then open a separate browser window (like in Chrome or Safari)
• Go to http://YourSite.com/dap/loginAs.php

On that page, you will see 3 form fields as shown in the image below:

1) Email address of user/member that you wish to log in as
2) DAP Admin Email
3) DAP Admin Password

So once DAP verifies that it is indeed the DAP Admin trying to log in as someone else, DAP will log you into the site as that member whose email id you entered in (1) above.

NOTE: The Log In As Member (LIAM) feature does NOT mean that you can use just one browser to log in as both DAP Admin and regular member. You still need to use two separate browsers – one for DAP admin (like Chrome) another for regular member (Firefox). All LIAM does is to give you a workaround for logging in as someone else, because starting 4.4, the DAP Admin can no longer see what the member’s password is in order to log in as them.

Approving Users Before Access Is Enabled

Problem

“Will DAP allow me to manually approve members before their new accounts are activated? The process should be…
a) new user signs up, DAP prompts that the account is pending approval
b) Admin approves the account manually and email is sent to new member with their password and login details”

Solution

Yes, this can be achieved by enabling the “Double Optin” for a product.

So, normally, when a DAP Product is made “Double Optin” by entering the double-optin subject and email text on the “Email Notifications” tab of the product, and a user signs up for this product (whether as a free sign up or as a paid purchase or Admin-add), DAP will send them the content of this double-optin email first.

And usually, the body of this email would contain the %%ACTIVATION_LINK%% merge tag, which would become the confirmation link that the user has to click on first, before their product access status becomes “Active” (from “Inactive”). And as soon as the user clicks on the confirmation link, their product status becomes active, and then the “Welcome Email” is sent out right away, and now the user can log in and start accessing the content that is protected as part of that product.

Using Double-Optin To Force Approval

If you make the DAP product as double-optin, and remove the merge-tag %%ACTIVATION_LINK%% from the email body, what happens is that the user/member will get the email, but there’s really no activation link (confirmation link) in the email for them to self-activate their account. So the email would just say something like…

“Thank you for your purchase/signup. Your account needs to be activated by us. So appreciate your patience while we do so”.

Now, their account remains at “Inactive” status. And only you, the DAP Admin, can activate it.

By now, you would’ve gotten the admin notification email for this person’s signup. So you know their email id. If not, you can just go to DAP > Users > Manage and you’ll see all inactive users.

You would then click on “Modify” to activate product access. And if the user status is also “Inactive”, then you would edit the user info, and change their status to “Active” (from “Unconfirmed”).

And then make sure you’ve added an autoresponder email (that contains the user’s email and password – insert mergecodes %%EMAIL_ID%% and %%PASSWORD%% into the email) to go out on Day #2 for that product.

And assuming you will be approving this new user at some point within the first 2 days, the autoresponder email for day #2 will get triggered within the hour as soon as you activate their account, and the user will get their welcome email.

Or you can send them the password in the double-optin email itself, but tell them that they won’t be able to log in just yet until their account is activated. It’s all up to you – DAP is as flexible as you need it to be.

So that’s how you would use the Double-Optin feature to indirectly force an “Approval” process.

Credit Store Setup

Credit Store Setup

The document below explains how to setup this plugin after you have installed it using these instructions.

Please NOTE:
1) The prerequisite for using this plugin is you must be on DAP 4.5.2 or above. It is not supported by older versions of DAP. If you are not on dap 4.5.2 or above, then please make sure to first upgrade to the very latest version of dap and then follow the steps below to install the DAP Credit Store Plugin.

2) Credit Store is NOT backward compatible with old plugin called SSS (Self-Service-Store). If you are using the very old SSS plugin and upgrade to CS, you will have to start over with new CS as the data stored in SSS tables cannot be migrated over to the CS tables and your old SSS plugin will no longer work after the upgrade to new CS.

3) If you are already using the OLD Credit Store plugin, then please contact us before you upgrade to the new CS as the new CS has a completely different store front user interface (UI). If you are ok with upgrading to the new and much improved look&feel, please make sure to first take a full database backup of the dap database and a backup of your dap and daplivelinks folder.

Steps to setup the Credit Store:

1. Enable Credit Store

Set DAP admin -> setup -> config – > Credit Store -> Enable Self-service / Credit Store to “Y”.

2. Credit Store Front Layout /  Templates

Visit this page for detailed documentation on this.

2. Create a Credit Store Front page

Login to WP admin -> Add New page -> Visual Editor -> You will find a new CS Editor button. Click on that to configure storefront options.

Visit this page for detailed documentation on this.

3.  Create Product Category in DAP admin -> Add / Edit Product Category page

Visit this page for detailed documentation on this.

4. Create Master Product

Visit this page for detailed documentation on this.

5. Enable self-service for the master.

After you create the master product, go to DAP Admin -> Credit Store -> Store Front Settings page.

Select the master product you created above and set the following values:

 – Is this the “Master” product? Set to “Yes”.

–  Redeemable with Credits?   Set to “No”.

– # of Credits the users will earn when they signup to this product or purchase this product (set it to whatever number of credits you want the users to earn when they signup or purchase this product.

–  # of Recurring/Subscription Credits assigned to this product

6. Create Child Product

Visit this page for detailed documentation on this.

7. Enable self-service for the child product(s).

After you create the child product, go to DAP Admin -> Credit Store -> Store Front Settings page.  Select the child product you created above (step #6) and set the following values:

 –  Self-Service allowed?   Set to “Yes”.

 – Is this the “Master” product? Set to “No”.

– Self Service Availability Start Date and End date (you can leave the default value for the start date (set to today/current date) and end date of 9999-12-31.).

– Allow credits to be redeemed at content level –  set to Y if you want to allow users to redeem credits for individual content instead of purchasing the entire product.

– Resell Product: Allow users to redeem already redeemed products ?  You CANNOT resell product if you allow ‘credits to be redeemed at content level’.

After a user redeems their credits against the product or against individual content, these products will disappear from store.

If resell product is “Y”, users will still see the product in credit storefront even after they have redeemed their credits towards the purchase of the product.

If resell product is “N”, users will NOT see the product in credit storefront after they have redeemed their credits towards the purchase of the product.

 – Product Image URL – must start with ‘http://’. If no images are set, the product will appear with no-image in the storefront page.

– Product Image URL Hyperlinked To:   what page do you want to take the user to when the users click on the product image.

–  # of Credits assigned to this product: this is calculated dynamically by adding up credits assigned to individual content if ‘allow content level credits’ is enabled.

If allow content level credits’ is “N”. the # of Credits assigned to this product is used.

8. Associate child product(s) to the category

Go to DAP products/Levels -> Credit Store page.  Associate child product(s) to any of the product category(s) created in step # 2.

You will find the option to associate child to master below the self-service-store options (under Add Products to Category).

NOTE: A credit store child product cannot participate in regular content dripping.  You cannot sell the same child product for $ as well as allow it to be redeemed using credits. You will have to use 2 separate products (one for regular dripping and the other for credits).

9. Configure Credit StoreFront page using CS editor

10. Testing

Now login to dap admin, go to dap admin -> add users page, give the admin user access to master product. Say the master product is assigned 10 credits.

Go to dap users -> manage page=> click on the ‘Credits’ field and it will show how many credits the user has.

Now go to the credit storefront page created in step #9.  You should see all the child products available for redeem (only child products that are associated to category will show up in the store).

You can redeem the entire child product, and go back and check dap users -> manage page=> click on the ‘Credits’ field and it will show how many credits the user is left with.

Credit Store Introduction

The Credit Store Plugin will allow you to sell “Credits” to your members, and then your members can “Redeem” those credits towards the purchase of any content you’ve made available in your  Credit Store. Similar to buying credits at Audible.com or earning credit card reward points.

The Credit Store plugin enables “Content On Demand“. Instead of you dripping content on your members in a pre-determined fashion, they choose the modules they want, and the order in which they want them. You just give them the credits putting the power of choice at their fingertips.

You can configure the plugin to Pay Affiliates by credits (for leads and sale) which they can then use to pay for their own purchases and subscriptions on your site.

You can also allow your users to earn ‘Social-Media-LIKE‘ credits OR ‘Comment‘ credits.

Credits are like currency, your users can use the earned credits to buy your entire product or buy individual content (pay-per-post-using-credits).

For ex, say you signup for an audible.com membership plan where you are awarded one audible.com credit a month. Most of the books on Audible can be “bought” for one credit, so you can usually get at least one book a month with your membership or you can accumulate credits for a few months and then go to the store to buy whatever products you want in exchange for credits. You can setup a similar storefront and rewards-program for your members instantly using our credit store plugin.s

Say you offer silver, gold, platinum monthly memberships. You can charge more for your gold membership than silver but offer more free credits as bonus. Similarly you can charge more for your platinum membership than gold but offer a lot more free credits as bonus. These users can then use the earned credits to browse your store and get content of their choice. So you can quickly setup a rewards program where you reward users based on the membership plan and your users will get automatic access to the rewards program when they enroll so they can start earning points and redeeming them at your store right away.

Members receive credits that can be used as currency on your site and applied to any purchase of products that you have made available in your store.

With the credit store plugin, setting up a storefront page (where your users can buy the product of their choice using credits) is a breeze. You can literally setup a storefront page in less than 5 minutes.

To summarize, the Credit Store plugin will allow you to create an Instant Credit Storefront Page where:

1) You (Site Owner) can display the products that can be redeemed for credits and

2) Your users can come to this page to Redeem their Earned Credits/Points.

Please read this document before you use this plugin.

Note: The prerequisite for using this plugin is you must be on DAP 4.4.x. It is not supported by older versions of DAP. If you are not on dap 4.4.x, then please make sure to first upgrade to the very latest version of dap 4.4.x and then follow the steps below to install the credit store plugin.

WARNING: If you are a self-service-store user and already have a lot of self-service-store users, then DO NOT upgrade to dap 4.4.x as it is NOT backward compatible with OLD SSS. We have completely revamped the old SSS plugin and now it’s called CreditStore (CS). We had to update the underlying dap scripts and dap tables/fields for the NEW CS plugin and it was NOT possible to make the scripts / tables work with both OLD SSS and NEW CS. If you can simply upgrade to 4.4.x and use the NEW CS plugin and manually give your existing SSS users access to new CS plugin, then it will work fine. There is NO automatic way to move old SSS users to new CS model.

Sell credits to your users

If you have a one-time (free or paid) or a subscription product, and you want to allow your users to earn credits when they buy the product or when a recurring payment comes in, then all you need to do is define / designate the product as Master in DAP products/levels- >Credit Store Front Settings page and ‘Assign Credits’ to that product (initial credits and recurring credits) in that page.

Here’s what you can do with the product defined as master (that allows users to buy credits).

1. The master product can be a regular full-fledged dap product that you sell. You can drip content (if reqd) under the master like any normal dap product. The only thing with product that you have set as master is in addition to doing everything a regular dap product does, this master product will allow your users to earn credits. If a user gets access to this product (via free signup or via purchase), they will get the credits assigned to this product. So you can use credits during a special promo and tell your users that if they signup or buy the product, they will earn credits in addition to the content that they are buying and they can use the credits in the store towards available child products. Or you can simply setup a master as a way for your users to purchase credits. It can be a dummy product setup just to allow your users to purchase credits. You can setup the payment button for master like you would for any dap product. DAP will know to automatically award credits to the user when the purchase is complete. You will find the assigned credits to user in the dap users->manage page under ‘Credits’ column.
2. Users that purchase the product designated as master, will earn credits assigned to that product and in addition, will also get access to any dripped content under the master.
3. Master product can be a one-time or a recurring/subscription product.
4. User-Level-Credits. The credits the users earn will be accumulated in the user’s account and they can use the accumulated credits towards ANY redeemable child products in the credit store.
5. Option to assign recurring credits : The users will earn recurring credits (if configured under DAP products/levels- >Credit Store Front Settings page) upon each subscription payment.

Provide different ways to your users to EARN credits

Users can earn credits in several different ways:

1. Signup to FREE product and earn credits (provided you have setup the product as master and assigned credits to it in DAP products/levels- >Credit Store Front Settings page).
2. Purchase one-time dap product and earn credits as bonus. Users that purchase the product designated as master, will earn credits assigned to that product and in addition, will also get access to any dripped content under the master.
3. Purchase a membership / subscription product and earn credits every month (or every recurring cycle) if the product has recurring credits assigned to it.
4. Affiliate Lead Credits: Affiliates can earn credits for referrals that lead to signup (provided you have setup credits for the product in the DAP admin -> Affiliate -> Commissions page)
5. Affiliate Sale Credits: Affiliates can earn credits for referrals that lead to sale.
6. Comment Credits : Users can comment on a credit enabled page and if comment is approved (or if set to auto-approve), the user will earn assigned credits. This is NOT part of the core Credit Store Plugin. You will need our SocialCredits plugin to enable Social Media credits.
7. Social Media Credits :  Users can LIKE a page/post to a Social Media Source (Facebook, Twitter, Linkedin, G+) and earn assigned credits. DAP Admin can assign different number of credits for each Social Media Source. For ex- Facebook like can be assigned 10 credits, Twitter can be assigned 5 credits etc. This is NOT part of the core Credit Store Plugin. You will need our SocialCredits plugin to enable Social Media credits.

Setup Products redeemable in the store

1. Redeemable products need to be defined as ‘Child’ in the Credit Store configuration (DAP products/levels- >Credit Store Front Settings page)
2. All redeemable products will automatically appear in the store (depending on Credit Store settings in DAP products/levels- >Credit Store Front Settings page).
3. Resell products: By default, if a user has already purchased a product, it will automatically disappear from that user’s view of the credit store. If you want the users to be able to redeem the same product for credits again, then set resell product setting to Y in the DAP admin -> Credit Store page.  If you allow ‘content-level-credits‘ for your child product in the Credit Store Front Settings page in dap admin , then you cannot set ‘resell’ to “Y”. The resell to “Y” can only be used if you only allow users to redeem entire product and do not allow users to redeem individual content setup under that product’s “content responder” section.
4. Pay-Per-Post using credits: Accomplish this via content-level credits. User will have the option to either redeem their earned credit to get access to the entire product (in this case they will get access to all content available under that product) OR they can redeem access to individual pieces of content (page / post / video / resource) under that product. Content-level credits can be enabled in dap admin -> products/levels -> credit store front page.  Users can pay for the post / page / resource of interest using credits (instead of $).

Setup Product Category

1. Define a category for the ‘Redeemable products‘ in the Credit Store.  The category is ONLY used for display purpose in the store. If you do not define a category, and do NOT assign the products that you want to be associated to that category in the  DAP products/levels- >Credit Store Front Settings page, then NO products will show up in the Credit Store Front end. So make sure to setup a product category (DAP admin -> Products / levels -> Add/Edit Credit Store Category page) and then go to DAP products/levels- >Credit Store Front Settings page and associate the child products to that category. For example – you could have an internet marketing category and associate your facebook secrets, twitter secrets products to that category.
2. You can display single category per credit store page OR you can display all the categories (and redeemable products belonging to it) on the same Credit Store page. You can create a category-level credit store page where only products belonging to a certain category shows up on that page. OR you can create a generic credit store page where products belonging to ANY category shows up.

Credit Store Page Layout – Front End

You can use a ONE product per row layout OR you can use MULTIPLE Products per row layout for your credit store front-end page.

If you have ‘content-level-credits’ enabled (pay-per-post) for any of your child product, then you can ONLY use ONE product per row layout  because MULTIPLE Products per row layout will only allow for simple product boxes per row, it wont allow the complex layout that products that allow content-level-credits require.

Create Credit Store Page – Front End

After you install the plugin, you can go to the WP Admin -> Pages -> Add New – > Visual Tab -> You will find a new Editor Button called ‘CS’. You can click on that button and you will find ALL the credit store front end page setup options. Its self-explanatory.  Once you have completed the setup of the page, you can publish that page and it will become the page where logged-in users can come to redeem their earned credits.

Click here for details on the various Credit Store Editor button option.

Credit Store Installation

The Credit Store plugin will allow you to create an Instant Credit Storefront Page where:

1) You (Site Owner) can display the products that can be redeemed for credits and

2) Your users can come to this page to Redeem their Earned Credits/Points.

The document below explains how to install this plugin.

Note: The prerequisite for using this plugin is you must be on DAP 4.4.x. It is not supported by older versions of DAP. If you are not on dap 4.4.x, then please make sure to first upgrade to the very latest version of dap 4.4.x and then follow the steps below to install the credit store plugin. If you have purchased our Credit Store plugin, then please follow these steps to install the plugin:

1. Go to wickedcoolplugins.com/login.
2. Download CreditStore.zip to your desktop.
3. Now install this plugin in your WP admin panel like any other WP plugin. Go to WP admin -> plugins -> Add New -> Click on the ‘Upload’ tab -> click on browse to find he downloaded CreditStore.zip from your desktop.
4. Click on Install.
5. Go to WP Admin -> Plugins -> Activate this plugin

Gift Subscriptions

There are two ways members can buy gift subscriptions for others.

1) Use the recipient’s email id (but their own name and billing info) during checkout. So when DAP creates the member account, it will send the welcome email to the recipient’s email id.

NOTE: Using the recipient’s email id may not be an option if the gift giver is paying for it using their own Paypal standard account, in which case their Paypal email id will be used by DAP to create the membership account. So, the best option is the one explained below.

2) BEST OPTION: Have the buyer make the purchase in their own name, and then forward the welcome email (which has the password to the member’s area) to the recipient. And the recipient can then log in using that information, and can change any and all profile information on the User Profile page.

NOTE: If this is a subscription product, then the recipient should not change the “Paypal Email” field in the profile, which will be having the buyer’s Paypal email id, because recurring subscriptions will continue to come in using the buyer’s Paypal email id. And since the recipient is not the one being charged, and it’s still going to be charged to the gift giver’s account, they need to leave that field in there. So you can use the [DAPUserProfile] shortcode and maybe not even show the “Paypal Email” field.

Automated Email Dripping

In dap 4.4, we have added a new feature where when you setup content for dripping, dap will automatically setup an email auto-responder to drip corresponding to each dripped content. The autoresponder drip setting will match the content drip setting. When you enable the automated dripping, an email will automatically get dripped ( you will find it in dap products page -> autoresponder tab) for every content you have dripped. An automated email alert will get sent to your participants and you can configure what you want in that email in the dap setup->templates section.

You can configure/customize the email you want sent automatically when any content is dripped and the email will automatically get sent at the top of the hour (when dap hourly cron runs).

But there are a few things that it does not support :

1) You cannot control what type of content should result in automated dripping (post/page/files etc). It will apply to all dripped content.

2) If you have content already dripped before you install the autodrip module, then when you install the autodrip, it will get a list of ALL of your dripped content .. even the ones you had dripped in past (and not just the ones you drip from that point onwards).

And it will set up an automated email to drip for each of your post/page regardless of when it was actually created. in this release, you CANNOT set a point in time to make the autodrip apply to posts created only after that point in time.

3) When automated dripping is configured, it will apply to all products. You cannot configure it at product level. It’s a global setting. So any post/page you drip under any product.. an automated email will get setup for that page/post. If you have product A and B, then you cannot have the autodrip only apply to say product A. It will automatically apply to both products – A and B.

4) You cannot use it if you are ALSO using SSS/ Credit Store. It’s not compatible currently.

Here’s how it works :

If you have a content set to drip day 10 as shown below:, then an automated email will get setup and it will get sent to users that’s on day 10 of their membership. If you have new users that just joined, they will not receive the email until they reach day 10.

If you have content set to drip day 1 as shown below:

Then an automated email will get setup (as shown below) and it will ONLY get sent to users that’s on day 1 of their membership. If you have new users that are on day 2 or more, they will never receive the email as they are already past that drip day.

Setup Instructions :

Just like the hourly dap cron (dap-cron.php), you will have to configure another cron for autodripping.

The name of this cron script is  /dap/dap-autodrip.php. You can configure it to run once every 1/2 hour. This way it will pick up any new posts added in the 1/2 hour and create autodrip entries for it.

Say your cron command for the hourly dap cron (dap-cron.php) in your webhost cpanel -> cron tab is :

/usr/bin/php /var/html/wordpress/dap/dap-cron.php

Then for autodrip, the command will be:

/usr/bin/php /var/html/wordpress/dap/dap-autodrip.php

Set it up in your webhost cpanel -> cron tab to run once every 1/2 hour. Everything for this cron will mirror the dap-cron.php except the name and it will run once every 1/ 2 hour instead of once every hour like dap-cron.php.

Here’s how can test this feature :

1) Lets say you have a NEW product
2) Now add a new user to that product via dap admin -> add users page
3) Now say you dripped testpost1 under that product. Set drip start day = 1
4) Now go to autoresponder tab and make sure there are NO automated emails set for drip
5) Now either wait for the dap-autodrip.php cron to run (depending on whether you set it to run once every 1/2 hour or 1 hour)
OR
For testing purpose, you can run the cron manually by visiting this URL in a browser:
http://YOURSITE.com/dap/dap-autodrip.php

6) After you run it manually or after it runs via cron, if you go and check the Email Autoresponder tab for that product, you shd see a new AUTOMATED autoresponder email dripped for that testpost.

7) Now wait for the main dap cron job to run. It will run once every hour.
When it runs the email will get sent. To make sure email got sent, go check dap system -> job queue. See if you find the email there with “completed successfully” status. If yes, the email got sent and you are all set.

NOTE: If you dont want to wait that long and want to quickly test it, then just run dap-cron.php manually by visiting this URL in a browser:
http://YOURSITE.com/dap/dap-cron.php

Access Expiration Options

In DAP 4.7, we have added a new feature to the hourly dap cron where once every day (it’s hardcoded to run ONCE between 10:00 PM – 11:00 PM PDT) the cron will look for users whose access expired that day.

You can configure the Cancellation Options in DAP Products page -> Cancellation & Expiration tab.

Then based on these settings, the DAP Hourly Cron will check if the current time is between 10:00 – 11:00 pm PDT (Server time), and if yes, it will take a look at each product, pick up the ‘Expiration Action’ setting for that product, then get a list of ALL users whose access to that product has expired and apply the ‘Expiration Action’ to that user->product record in DAP users -> manage page.

The reason the DAP Cron checks the current time and runs the ‘expiration job’ only once a day is because running it too often will burden your server/resources as this job needs to pick up all products and then apply the cancellation rule to all users whose access has expired.

The main thing is to make sure it only runs once.. does not matter if that’s between 10 – 11 or 11 – 12 etc. We just picked the time to be between 10 – 11 PM (server time).

1) No Action

User’s access will auto-expire at the end of current recurring cycle. If the user re-signs, they will start from where they left off instead of starting over at day 1.
Infact this is how all older versions of dap already work.

If a user cancelled access to a subscription product before and say that the same user now wants to start back after a couple of months break.
If you have selected NO ACTION as this product’s expiration setting (in dap products page -> cancellation & expiration tab),
then when the user re-signs, they will start their dripping from where they left off and will not start fresh again from day 1.

Say a user’s access start date is 07/01/2014 and access end date is 07/30/2014, when the cron runs on 07/31/2012
and finds the user’s access has expired, it wont do anything.

If the same user re-signs for the same product on 08/30/2014 using the same email id, their access start date will be what it was before (07/01/2014) and their new access end date will simply be extended from what it was before. It will be set to previous access end date (07/30) + 30 days instead of new signup date (08/30) + 30 days. User’s access to product will remain expired. You will have to set post-expiry access to “Y” in dap setup->config page for access to ‘paid-for content’.

See this for more details: Cancellation

2) Remove From Product

If selected, dap will automatically find users whose access to this product has expired and remove user’s access to product completely for those users.
You will need this setting to prevent access for expired users. Users will completely lose access to product.
If these users signs up again, they will start over like a new member.

3) Set end date to previous day

To enable this option, you will have to first enter the following in /dap/dap-config.php file.

Please ftp to your site, find dap-config.php file, edit it and add this to your /dap/dap-config.php file:

Add it towards the top after php start tag (<?php) :

if(!defined(‘EXPIREACCESS’)) define(‘EXPIREACCESS’,’Y’);

IMPORTANT:  Replace all occurrences of backticks in the line above with single or double quote character.

Then upload back to your site (under dap folder).

We are forcing the dap-config.php setup in DAP 4.7 so users do not pick this option by mistake. We also want this feature to be BETA tested fully (in DAP 4.7) and then we will remove the extra steps (to add lines to the dap-config.php).(

After you set this in dap-config.php, this dropdown option will be available in the ‘expiration action’ dropdown.

If you pick this option for a product, then DAP CRON will automatically find a list of expired users (whose access has expired to this product) nightly and move the expired user’s access start and end day (set the access end date to the previous date).

When the cron wakes up and runs this job once once every night at 10:00 PM, it will move the user’s access start / end date forward in such a way that user’s access will remain expired but the access end date will not be stuck somewhere in past. It will be always set to the previous date (from current date).

Say a user’s access start date is 07/15/2014 and access end date is 08/15/2014.

When the cron runs on 08/16/2014 and finds the user’s access has expired, it will set the access end date to previous date.

So first time when the cron runs after the user’s access expires, nothing will happen. The access end date will remain 08/15 as it’s already set to previous date.

When cron runs on 8/17, it will move forward the the access start and access end window, so the new access start date will be 07/16 (moved forward by 1 day) and end date will be 8/16 (moved forward by 1 day).

This way the user’s access is still expired (as it’s always set to previous date) but the access dates are not stuck in the past.

If they re-sign, when DAP extends access, the access end date will be in the future instead of being expired.

If the cancelled user re-signs, the user’s access will not remain expired as their access will be extended from the current access end date to a date in future and the dripping will continue from where they left off.

IMPORTANT:  ADDITIONAL INFORMATION

1)  EXPIRATION: SET ACCESS TO PREVIOUS DATE

We recommend that you enable this option ON a test product first. DO NOT use this option on an actual live product. Add a few test users to the test product. Move their access start/end date manually to a date in the past .Make a note of it. Enable the admin option to ‘move date to previous date’ for this product. Then run the cron manually. Go back to dap manage users page and check the new access start / end dates for these users. If all looks good, then use it for live products.

2) CRON JOB:

The dap cron (dap-cron.php) runs once every hour at the top of the hour… but it will only do the expiration job between 10- 11 PM (server time). The expiration part of the cron only executes once a day.

To force run the cron, run this command in a browser (dont run cron too close to the top of the hour as it will collide with the normal running of cron ).

http://yoursite.com/dap/dap-cron.php?forcerun=Y (replace yoursite.com with the name of your site)

Product Cancellation/Expiration Options

AuthSMTP Integration

If you’re having email delivery issues on your host, you can connect DAP to 3rd-party email systems like Amazon SES and AuthSMTP.

In this article, you’ll see how to integrate DAP with AuthSMTP.

1. Signup for an account at AuthSMTP
2. Log in to your AuthSMTP account
3. Go to Registered From Address tab
4. Take the email id from DAP Admin > Setup > Config > From-Email Id and enter that email here and register it here (basically, you’re whitelisting your DAP Admin email id as a registered sender – if you don’t do this, AuthSMTP will reject and discard all emails sent via DAP). You will need to “Confirm” the registration by clicking on an activation link that they will be sending you.
5. In your AuthSMTP account, go to SMTP Details tab.
6. Make a note of the SMTP Server (usually mail.authsmtp.com), SMTP Username, SMTP Password.
   
7. Now log in to DAP Admin, and go to Email > SMTP
8. On this screen, use the section Add a New SMTP Server to create a new SMTP row as follows:
   Description: AuthSMTP
   Server: mail.authsmtp.com (or from Step 6 above)
   Port: 2525 (must be exactly that)
   SSL: N (must be exactly that)
   User Id: Your AuthSMTP Username (from Step 6 above)
   Password: Your AuthSMTP Password (from Step 6 above)
   Email Sending Limit Per Hour: 500
   (Max 500 if on shared server. Max 2000 if VPS or dedicated server)
   Activated: Y
9. Click on the “Add” button to create and save the new AuthSMTP server setting.
10. And now you should see two rows under Manage Existing SMTP Servers: One for “Local Web Host” and another for “AuthSMTP”.
11. For the “Local Web Host” row, be sure to set “Active” to “N” – because now that you have set up AuthSMTP, you want all instant welcome emails, autoresponder and broadcast emails to be sent out through AuthSMTP, and not your web host’s email server.

That’s it!