I've got a members area on a site, which just uses an standard asp:login element.
But i've noticed that after the first login, a auth cookie is set, but the asp:LoginStatus still says "Login", instead of showing as logged in. Then after logging in again it shows as "Welcome! membername".
I noticed there was a couple of threads talking about lines that needed to go in the web.config but these look like they are already in there.
What happens if you login once and then refresh the page afterwards? Perhaps you need to redirect to another page after you have sucesfully been logged in?
If you refresh the page it still does not show as logged in, and does not allow access.
If I navigate off that page and then back, it still shows as not logged in, however the auth cookie still exists.
The only thing that seems to work is if you click the "login" button after entering username/password, instead of hitting enter, the page then refreshes and shows as logged in. Very confusing, there are other forms on the page though so hitting enter must initiate those instead of the login form, but the auth cookie still gets created, strange.
Login twice on members area
I've got a members area on a site, which just uses an standard asp:login element.
But i've noticed that after the first login, a auth cookie is set, but the asp:LoginStatus still says "Login", instead of showing as logged in. Then after logging in again it shows as "Welcome! membername".
I noticed there was a couple of threads talking about lines that needed to go in the web.config but these look like they are already in there.
I'm on 4.7.1.
Is there anything I can check?
Thanks, Pete
Hi Pete
What happens if you login once and then refresh the page afterwards? Perhaps you need to redirect to another page after you have sucesfully been logged in?
/Jan
Hi Jan
If you refresh the page it still does not show as logged in, and does not allow access.
If I navigate off that page and then back, it still shows as not logged in, however the auth cookie still exists.
The only thing that seems to work is if you click the "login" button after entering username/password, instead of hitting enter, the page then refreshes and shows as logged in. Very confusing, there are other forms on the page though so hitting enter must initiate those instead of the login form, but the auth cookie still gets created, strange.
Pete
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.