We are going through our v12 upgrade and are looking at using LoginEx3 to login users when applying a promocode.
The API document says that it isn't an extension of LoginEx2, but we'd like to replace all uses of LoginEx2, so we're not juggling 2 methods. Is there any reason that we shouldn't use LoginEx3 for our regular, non-external authentication, assuming we pass bAlreadyAuthenticated=false?
Thanks,
Patrick
Hi Patrick,
I believe that LoginEX3 is designed to work with external authentication (Facebook) where a password is not required. But it looks like it has all the parameters that are in LogInEX2 (password is not required either). If you’re planning on using Facebook Connect in the future I would use EX3. You should probably check in with the network to be sure but that’s my take!
Gloria
From: Tessitura Web Forum [mailto:forums-tessitura-web@tessituranetwork.com] On Behalf Of Patrick FitzGerald Sent: Tuesday, May 06, 2014 10:14 AM To: Gloria Ormsby Subject: [Tessitura Web Forum] LoginEx3 Question
You were sent this email automatically because you subscribed to the Tessitura Web forum. You may reply to this message to post to the Web forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!
I've recently played with LoginEx3 in depth, and it seems to function identically to LoginEx2, provided that you pass parameters in the same combinations - and bAlreadyAuthenticated as false.
I'm curious what it means that LoginEx3 is not an extension of LoginEx2. Perhaps it's some under-the-hood detail that should be encapsulated and not our concern as consumers of the API.
IMHO If it ain't broke...but that's everyone's own decision
Unknown said: I'm curious what it means that LoginEx3 is not an extension of LoginEx2. Perhaps it's some under-the-hood detail that should be encapsulated and not our concern as consumers of the API.
It looks to use the same database objects so I believe that it is probably true.
I'm not on V12 yet so I can't see what changes were put in place but my guess would be WP_LOGIN has a switch operator for the boolean bAlreadyAuthenticated that is now passed.
As long as that switch is deactivating the new codebase/forcing authentication you should be all good.