It's simply called inside the header of each page so it returns logged in member's "frame" property each time it's called.
However, if I log into umbraco backend and change the property manually (saving member afterwards) it won't reflect upon the next refresh of the page...my guess is the of the results of the macro or even the whole pages themselves get cached...any way to aviod caching?
I've now got a MAJOR issue. Though most of it probably comes from my code, since I just now tested the custom made login control (made from loginview asp.net control) on another umbraco website I'm hosting on the same server and it won't work there either. User/pass just won't log me in.
First off, the Member.RemoveMemberFromCache(Member.CurrentMemberId()); line breaks everything (though it worked extremely well initially)...object not set reference error...Member.GetMemberId() returns null.
My guess is I'm doing it all wrong when working with members...but the documentation is a bit confusing...I've seen pages that for v4 (I'm using 4.0.3) you shouldn't use Umbraco API at all for membership, but how do I login members then please? AddMemberToCache is or it is not an option?!
Also, it worked perfectly before I managed to rename it to an existing .NET umbraco macro control's name, so I'm guessing there might also be some cache issues there, but since I used it on another website maybe not since I'm guessing two different umbraco websites (even though on the same Win2k8r2 server) don't share cache, or do they? How to reset the cache? Delete Temporary ASP.NET files or some xmls?
Unwanted caching XSLT macro results...
Here's a very simple XSLT which I made into a macro:
It's simply called inside the header of each page so it returns logged in member's "frame" property each time it's called.
However, if I log into umbraco backend and change the property manually (saving member afterwards) it won't reflect upon the next refresh of the page...my guess is the of the results of the macro or even the whole pages themselves get cached...any way to aviod caching?
solved it.
Only if someone could help me understand why, I'd be much grateful...
Followin this...or in other words by adding these two lines in front of my loginview control's login button click event which used AddMemberToCache:
Seems I spoke too soon...
I've now got a MAJOR issue. Though most of it probably comes from my code, since I just now tested the custom made login control (made from loginview asp.net control) on another umbraco website I'm hosting on the same server and it won't work there either. User/pass just won't log me in.
First off, the Member.RemoveMemberFromCache(Member.CurrentMemberId()); line breaks everything (though it worked extremely well initially)...object not set reference error...Member.GetMemberId() returns null.
My guess is I'm doing it all wrong when working with members...but the documentation is a bit confusing...I've seen pages that for v4 (I'm using 4.0.3) you shouldn't use Umbraco API at all for membership, but how do I login members then please? AddMemberToCache is or it is not an option?!
Also, it worked perfectly before I managed to rename it to an existing .NET umbraco macro control's name, so I'm guessing there might also be some cache issues there, but since I used it on another website maybe not since I'm guessing two different umbraco websites (even though on the same Win2k8r2 server) don't share cache, or do they? How to reset the cache? Delete Temporary ASP.NET files or some xmls?
Please help, thanks in advance.
is working on a reply...