DAP has a very powerful, flexible and easy-to-use log in flow for your users and members.<\/p>\n
And we call it the Smart Login<\/strong>, because the login process will work differently under different conditions, all designed to make the user-experience for your member more smooth and consistent with general login standards around the web.<\/p>\n So let’s see the various possible login locations in DAP.<\/p>\n But first, it is important to note that DAP has two main types of logins.<\/p>\n This is where it is considered a “generic” login by your member. For eg., a member came to your web site, and then just generally wants to log in to the member’s area – so they have no “context” – it’s NOT as if they were trying to view a specific page or post, got challenged with a login form, and then logged-in from there. That makes this a “Primary Login<\/strong>“.<\/p>\n Examples of this are…<\/p>\n a) Dedicated Login Page<\/strong>: You have a dedicated login page, like http:\/\/YourSite.com\/login\/ – which is what you’ve entered in to “Setup > Config > Login URL<\/strong>“. The body of this page has the DAP merge tag for the login form, which is %%LOGIN_FORM%%<\/strong><\/p>\n b) Login\/Logout Widget<\/strong> on any page of your web site. This is also considered a primary login. The reasoning here is that if they’re logging in through a sidebar widget, it means that they just want to log in to the member’s area, so it is considered primary login.<\/p>\n This is a login action that HAS “context”. Say, a member landed deep into your site (not the home page, not the dedicated login page) and were challenged by the “In Page Error Message” that says something like “Sorry, you must log in before you can view this content” and are presented with a login form right on that very same page. They were trying to read something before they were asked to log in first – which means, they must be returned to the same page they were trying to view BEFORE they were asked to login. So that makes this a “Secondary Login<\/strong>“.<\/p>\n Examples of this are…<\/p>\n a) Any custom “Error Page”<\/strong>, where you have inserted the DAP merge tag for the login form,\u00a0%%LOGIN_FORM%%.<\/strong><\/p>\n b) DAP’s “In-Page Error Message<\/strong>” which says “Sorry, this is private content – you must log in first before you can view this”.<\/p>\n c) Log in form showing up on a page when “Sneak-Peek<\/strong>” is enabled.<\/p>\n <\/p>\n Based on whether it’s a Primary Login or a Secondary Login, your member will be redirected to a different location.<\/p>\n 1) If it is a Primary Login action, then…<\/p>\n a) They’re taken to the “Post-Login URL” if set at a Product-level AND they have access to just one Product. This scenario is the only one where the Post-Login URL is ever used (whether it’s the Product-level or Global-level).<\/p>\n 1) If it is a Secondary Login action, then…<\/p>\n They’re always redirected back to the same page they were on (or were trying to access) before they were challenged to log in first to view the content.<\/p>\n Bottom-line<\/strong>:<\/p>\n Primary Login is predictable, and you (the DAP Admin) control where they go right after they login.<\/p>\n Secondary Login depends on “context”, and they’re taken back to whatever page they were on, before they logged in.<\/p>\n","protected":false},"excerpt":{"rendered":" DAP has a very powerful, flexible and easy-to-use log in flow for your users and members. Log in from a dedicated log in page, or Log in from the login form on the side-bar (login\/logout widget), or Log in through the log in form shown on “Sorry, you don’t have access to this content. Please […]<\/p>\n","protected":false},"author":4,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[12,3,16,27,20,58,31,54,65,43,33,26],"tags":[],"_links":{"self":[{"href":"http:\/\/digitalaccesspass.com\/doc\/wp-json\/wp\/v2\/posts\/1798"}],"collection":[{"href":"http:\/\/digitalaccesspass.com\/doc\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/digitalaccesspass.com\/doc\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/digitalaccesspass.com\/doc\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"http:\/\/digitalaccesspass.com\/doc\/wp-json\/wp\/v2\/comments?post=1798"}],"version-history":[{"count":13,"href":"http:\/\/digitalaccesspass.com\/doc\/wp-json\/wp\/v2\/posts\/1798\/revisions"}],"predecessor-version":[{"id":4901,"href":"http:\/\/digitalaccesspass.com\/doc\/wp-json\/wp\/v2\/posts\/1798\/revisions\/4901"}],"wp:attachment":[{"href":"http:\/\/digitalaccesspass.com\/doc\/wp-json\/wp\/v2\/media?parent=1798"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/digitalaccesspass.com\/doc\/wp-json\/wp\/v2\/categories?post=1798"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/digitalaccesspass.com\/doc\/wp-json\/wp\/v2\/tags?post=1798"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Primary Login<\/strong><\/h3>\n
Secondary Login<\/h3>\n
Redirection Rules<\/h3>\n
\nb) They’re taken to the GLOBAL “Post Login URL” (under Setup > Config) if you have NOT set anything at a Product-level, OR if they have access to more than one Product.<\/p>\n