[#6458] auto action condition first login

I am on 2.1.2+build.2017.02.08.01.14.28.ec3d63d1f but the [lastvisitdate] condition does not work. Still overriding the first login redirect. But to get back to the starting point of that: I need that only because the user does get redirected to the home page after login. I think it should be the default behavior that the user stays on the same page after login (just like it is done by the Joomla core).

The [lastvisitdate] condition [lastvisitdate] Not Equal To 0000-00-00 00:00:00 does not work in fields as well since the [lastvisitdate] get set before the condition is tested.

Please read the ticket details carefully to understand what was implemented. Nothing in regards to lastvisitdate was changed. What was changed is the variables available to the login triggers as noted in the ticket.

forge.joomlapolis.com/issues/6458#note-2

Specifically you could use onAfterLogin and condition that [var3] is equal to true to determine if it's first login attempt.

The [lastvisitdate] condition [lastvisitdate] Not Equal To 0000-00-00 00:00:00 does not work in fields as well since the [lastvisitdate] get set before the condition is tested.

The last visit date is updated during the login process and believe it also gets set on logout. That's simply how it functions. Please keep this in mind when trying to do any behavior on it.

Thanks but "[var3] is equal to false" fires on first login. So I still cant prevent an auto action to fire on first login.

And again: Why is CB not behaving like Joomla, meaning redirecting the user after login to the page he was on when he logged in? I would not have to deal with that whole thing at all.

Thanks but "[var3] is equal to false" fires on first login. So I still cant prevent an auto action to fire on first login.

Try conditioning against 1 or 0 instead of true or false.

And again: Why is CB not behaving like Joomla, meaning redirecting the user after login to the page he was on when he logged in? I would not have to deal with that whole thing at all.

CB does. Leave the login redirect URLs completely blank. If a return URL is available CB will use it. If one isn't sent with the URL (as &return=BASE64_ENCODED_URL) then it can't return them as it has no idea where to return them to. If this is not working edit "Community Builder System plugin" within Extensions > Plugins and ensure under Parse URLs you have the following configuration.

Redirect URLs: Enabled
Rewrite URLs: Enabled
Pass Return URLs: Enabled

Below is your original post in this topic and is all that bug ticket is aiming to address.

carin wrote: I have an "onAfterLogin" redirect action. How do I prevent that action from executing on first login after registration so it does not override the "First Login Redirect"-value in the cb configuration?

Sorry, I don't understand anymore what you're trying to do. Are you wanting a login redirect for first login only, but not regular logins? Are you wanting to return them on first login, but redirect them on subsequent logins? Please provide exactly what you're trying to do and how it's behaving so I have steps to reproduce and test your issue.

Thank you, 1 instead of true works.

I followed your hints and the CB login works like Joomla now. But when I put the login form in a modal it redirects to the homepage. That is why I needed the redirect action I explained in the first post.

Now I still have the problem with that other field that should only show up on the first login. How would I achieve that since the [lastvisitdate] is no option?

Now I still have the problem with that other field that should only show up on the first login. How would I achieve that since the [lastvisitdate] is no option?

I suppose you could have a checkbox field that you toggle to checked after a login that isn't their first login then condition against that checkbox field. Another option maybe 2 auto actions 1 that adds a usergroup if it's their first login then another that removes it if it's not their first login. Then you'd condition against that usergroup or a view access level that includes that usergroup. This would avoid needing a field for it and allows ACL usage throughout your site for first visit.