Now I have got two member groups. Each member groups has got a different view on the menu. I am using the following XSLT snippet to create the menu for the client area:
It works fine with public acces. So far there are no problems - each logged in member is just looking at the sites he is supposed to see. But now I want to show some user-specific information on the site. There are two users at the moment (One in group 1, the other one in group 2), with the ID's 1354 and 1451. However GetCurrentUser allways returns the the node with the ID 1451, even if the user 1354 is logged in!
If you are using v4.7.0 you might be having the Logout bug. You can either upgrade to version v4.7.1 or add a lougout button in a usercontrol to logout user completely.
You might also have a look at this threat, same issue as yours.
GetCurrentMember returns wrong node
Hi there umbraco community,
I've got a wired problem with the umbraco library function GetCurrentMember(): It returns the wrong member node.
I'm handling user logins using the standard ASP.Net LogIn control. Here is my code from the template:
Now I have got two member groups. Each member groups has got a different view on the menu. I am using the following XSLT snippet to create the menu for the client area:
It works fine with public acces. So far there are no problems - each logged in member is just looking at the sites he is supposed to see. But now I want to show some user-specific information on the site. There are two users at the moment (One in group 1, the other one in group 2), with the ID's 1354 and 1451. However GetCurrentUser allways returns the the node with the ID 1451, even if the user 1354 is logged in!
I guess there is some problem with caching caused by the way I am handling login's. Is there anything I am doing wrong?
Thank you,
- Carsten.
Hi Carsten,
If you are using v4.7.0 you might be having the Logout bug. You can either upgrade to version v4.7.1 or add a lougout button in a usercontrol to logout user completely.
You might also have a look at this threat, same issue as yours.
//fuji
Thank you, Fuji. I've updated to umbraco 4.7.1 and now everything works fine! :-)
is working on a reply...