Someone should build a plugin that redirects to previous page after user logs in when he clicks to add new listing, adds new comment, etc.
Right now it redirects to account page and it’s useful.

I think it's trying to redirect to previous page, but previous page is login page.

I think it's trying to redirect to previous page, but previous page is login page.

Previous page meaning the page you are coming from, before going to login page. For example you click to add a new listing, it takes you  to login page and after log in it takes you to my account. This has no logic whatsoever, it should redirect to the page you were initially going to.

That's not previous page already and it's not possible to provide this page to login controller as it's not http referrer.

That's not previous page already and it's not possible to provide this page to login controller as it's not http referrer.

It should be saved in a cookie or session because this is a must. Think about it, you click to add a listing, it redirects to login page and after you log in it redirects to account page instead of the page you originally went from.

That could be most probably insecure method, but will review it again.

That could be most probably insecure method, but will review it again.

This has to be rethinked. Another example is when you want to send a message(instant message) to a seller. You visit listing page, click to send a message, you are redirected to login page and after you log in you get redirected to account page, not to the “send message” page. It’s terrible for the user, he has to go back 2-3 times to go back to listing page to send message.

This is on my todo list ... ideally, a login overlay (version of login page) should be presented and the same page the user is on is refreshed after successfully logging in. No need for redirects or implementing insecure methods.

@wiz
That usually does not work well with recaptcha and social logins.

@wiz
That usually does not work well with recaptcha and social logins.

Workaround for captcha/recaptcha is to trigger verification only when user starts inputing text, making selection or submitting, not on page load.

As for social logins - I don't use it but I'm sure there's a workaround for it too (what's the issue anyway?)

If refreshing the page is an issue then ajax could be used to login with secure/encrypted backend validation, no?