Entries Tagged 'Access Control' ↓
May 12th, 2013 — Access Control, Config, Customization, Setup
If you are using double-optin for your DAP product, then you would normally have entered the text %%ACTIVATION_LINK%% in your email body, which is replaced by a unique confirmation link specific to that user.
Normally, when that activation link is clicked, the user is redirected to your login page configured under Setup > Config > Login URL.
But if you wanted them to be redirected elsewhere to a page of your choice, then in your double-optin email body, where you normally enter %%ACTIVATION_LINK%% , enter this instead:
Where “http://link/to/landing/page/” is the URL where you want them to be redirected to after they click on the double-optin activation link.
April 27th, 2013 — Access Control, Passwords, Security, Setup, Users
DAP has a security check to prevent password sharing.
And starting DAP v4.4, you can turn this off at both a per-user level and also at a global site-wide leve.
Disabling IP Check For Individual Users
- Search for the user on the Users > Manage page
- Click on their email or user id, and you will now be taken to the “User Edit” page
- There, on their user profile, towards the bottom, set the field “Exclude from Login IP Check” to “Yes” and save.
This user will now be excluded from login IP check.
Disabling IP Check For All Users (Site-wide)
If you wish to permanently disable this for all users in your membership site, then here’s how to do it:
- Go to DAP Admin > Setup > Config
- Set “IP Login Limit: Max. # of User Logins From Different IP’s” to a high number – like “100″.
- Set “Flush Login IP Records How Often? Every….. ?” to “Day” so that any accumulated IP records gets flushed every day.
February 6th, 2013 — Access Control, Admin, Content Protection, Examples, OptimizePress, Setup, Troubleshooting
If you’re using OptimizePress as your theme, make sure you’re only using membership templates that have the word “DAP..” in them.
DO NOT USE any template that has the words “WP” or “WP Secured“. That will cause members logging in via DAP, to not be able to access those pages.
Those templates are meant for OP’s own internal membership functionality, or built for other membership plugins. Those will not work with DAP.
Templates that are OK to use with DAP
- Members 1 Content (Free/DAP/WL)
- Members 1 DAP Login Page
- Members 1 DAP/Wishlist Error
- Members 1 General Page (Free/DAP/WL)
- Etc.. anything with the word “DAP” in it.
For the other squeeze page/sales page templates, it doesn’t matter which ones you pick.
This restriction applies only to the “Members…” templates.
January 15th, 2013 — Access Control, Autoresponders, DAP, Email, Email Resources, Renewal, Setup
We have a new feature starting DAP v4.4: “Reverse Dripping”
This is where you can drip emails “X” days (where “X” is a number of your choice) before the access to a product ends for a member. So this is what you would use to send expiration notification / renewal reminder emails to your members.
To setup a renewal reminder email, you would set up the email as usual, and drip it as a negative day. So if you set up the email to drip on Day “-1″, then it means the email will be sent out 1 day prior to product expiry (for that product).
If you set it up to drip on “-3″, it will be sent out 3 days prior to access end date.
If you set it up to drip on “-7″, it will be sent out 1 week prior to access end date.
Renewal Reminder Email Setup
Warning: This is something you should set up only for recurring products that require manual renewal. Do not set up these emails to go out for automated subscription products, because the members will be charged automatically on the designated day every month, and asking them to renew will only confuse them.
- Create a new Autoresponder email with the product expiration notice, at Email > Autoresponders. In this email, you would say something like “Hey, your subscription is expiring in 1 week, so click on this link to renew… (followed by link to renewal page)”.
- Create another email that says “Hey, your subscription is expiring tomorrow…”.
- Go to Products > Manage and choose product for which you wish to set up renewal reminder.
- Switch to “Autoresponder” tab.
- Select the 7-day renewal reminder email from step 1 and add it to the product.
- Then click on the “Edit” link and set the drip day as -7
- Do the same for the 1-day reminder email as well, and this time set the dripping to be “-1″.
January 5th, 2013 — Access Control, Admin, DAP, Setup, Testing, Troubleshooting, Users
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.
December 16th, 2012 — Access Control, Activation, Admin, Examples, Merge Tags, Setup, Strategy
“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”
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.
November 23rd, 2012 — Access Control, Cron, DAP, Examples, Products, Setup
In DAP 4.4.3, 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 10/01/2012 and access end date is 10/30/2012, when the cron runs on 10/31/2012
and finds the user’s access has expired, it wont do anything.
If the same user resigns on 11/30/2012, their access start date will be what it was before (10/01/2012) but their new access end date will be 10/31/2012 + 30 days (instead of 11/30/2012+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. User will completely lose access to product.
If the user signs up again, they will start over like a new member.
3) Set end date to previous day
Automatically 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 daily, it will keep moving 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 would be always set to the previous date (from current date).
Say a user’s access start date is 10/01/2012 and access end date is 10/30/2012, when the cron runs on 10/31/2012
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, access end date will remain 10/30,
but when cron runs on 11/1, it will now move the access end date to previous date so the new access start date will be 10/02/2012
but end date will be 10/31/2012 (the access start / end block is moved forward).
So if the cancelled user re-signs, the user’s access will not remain expired as their access will be extended from the access end date
to a date in future and the dripping will continue from where they left off. You would probably want to use this setting if you are on DAP 4.4.
IMPORTANT: ADDITIONAL INFORMATION
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)
EXPIRATION: SET ACCESS TO PREVIOUS DATE
We disabled the ‘SET ACCESS TO PREVIOUS DATE‘ (one of the drop-down options in the ‘cancellation’ page) due to a bug. We have fixed the bug in dap 4.4.3 but the option is still disabled as we only want to make this feature available to dap owners / admin that ask for it so we can educate the dap admin on this feature better and test it on their site before they go live with this feature as we dont want the results to be something that the admin did not expect.
If you want the ‘expire – set to previous date feature’, pls contact us via support ticket, so we can put back the original admin option that will allow you to set the ‘set expiry to previous date’. Remember when you use this feature, both access start and end date will move forward… so say that the user’s access start date is set to 01/01/2013 and access end date is set to 01/04/2013 ( 3 day difference). Today is 2/11/2013. Now when the cron runs, it will move the access end date to 02/10/2013 (previous date), but it will also move the access start date to 02/07/2013 (3 days before access end date) as it moves the entire block (start and end date) forward. So you will lose the history… the fact that the user actually joined on 01/01/2013. Of course you can always find that in the dap payment processing -> orders page. So remember this when you use this feature.
If you are ok with this, we will enable this drop-down option on your site, then you can then 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 take a full backup of your dap database before you use this option on a LIVE product.. just in case the dates get messed up.
Q: Will the “delete user from product” option also delete from WP?
A: No, it will not delete from WP. It will only delete from dap.
November 20th, 2012 — Access Control, Admin, Content Dripping, FAQ, Protection FAQ, Setup, Strategy, Testing
We do NOT recommend testing what your regular member’s user-experience, while you are logged in as DAP/WP Admin.
Being logged in as DAP Admin and WP admin gives you certain privileges that your regular user/member won’t have. So you may see things that your members won’t be seeing. Or you may not see things that a regular user would normally see.
Either way, you may not be seeing what you’re supposed to see when you mix user testing with admin privileges.
So we recommend that you use two completely different browsers for testing: say, Chrome (or your primary browser) for WP & DAP Admin, and Firefox (or other) for logging in as regular user.
That way, you won’t have to keep logging in and out of DAP and or WP to test as both admin and user.
Keep them both separate.
November 8th, 2012 — Access Control, Admin, Content Dripping, Content Protection, File Resources, Protecting Content
Once you have protected content by adding it from left-to-right on the “ContentResponder” tab of the Products > Manage page, you can set the dripping day/date and link display text and other drip options, by launching the “Drip Settings” popup (see “1″ below) by clicking on the “Edit” icon next to the content you wish to drip.
By default, when you add any content (WP page/post or file), it is set to drip on day #1 by default. Which effectively means “no dripping” – and that the content is available to the member from day 1 of their purchase/signup.
1. Shows the “Edit” icon on the “ContentResponder” tab, and clicking it will bring up the “Drip Settings” popup (that shows 2, 3 & 4).
2. On the drip settings popup, the “Link Text” refers to the display text of the link that will be shown to the member on the “My Content” page.
3. If you wish to protect a link, but just NOT show it in the list of links on the “My Content” page, then set this to “No”.
4. Drip Settings: In DAP, you can drip content by Day, Date or restrict access by # of Clicks. You can only choose one method (eg., you cannot drip by day and date at the same time).
October 29th, 2012 — Access Control, Examples, FAQ, File Resources, Products, Protecting Content, Protection FAQ, WordPress
Now, normally, links to pages or posts show up in the left-hand side of the ContentResponder tab of the DAP Product only after they’ve been published.
But sometimes, for whatever reason, you may wish to protect pages or posts even before they are published – like in a “Draft” or “Pending Review” status. So here’s what you do.
As soon as you first create a new post or page, and tab out of the title field, and even before you save the post as a draft, or publish it, WordPress will create and display the permalink for that post/page, based on the text in your title.
So, if your page title is “Protecting Draft Pages”, then the default permalink will take on the structure http://YourSite.com/protecting-draft-pages – basically a lower-case version of the title, with hyphens separating the words. Like this…
You can then copy that entire permalink from where it is displayed, go to the DAP Product’s ContentResponder section, scroll down to the section that says “Protect a URL”, and then paste the entire permalink there (http://YourSite.com/protecting-draft-pages), and click “Add URL”.
That will protect this page or post in advance of it being published.