I've checked that Member.GetCurrentMember create a new Member from the database if it is not found in the cache. So, I expect to have the new member with its new properties in the cache now.
Then, the user is redirected to an other page, which call a xslt file for displaying some personnal informations (name, ...):
GetCurrentMember : xslt vs C# : caching
Hi All,
I have a first page, calling a C# usercontrol, where a user can change his personnal informations.
It contains a Save button, that update the properties (those value can be seen in the database) and, to force uncaching, finish by
I've checked that Member.GetCurrentMember create a new Member from the database if it is not found in the cache. So, I expect to have the new member with its new properties in the cache now.
Then, the user is redirected to an other page, which call a xslt file for displaying some personnal informations (name, ...):
But I still get the old values. It seems as if the cached values have not been reloaded.
Is it something know and is there any way to fix it?
Thanks
Which version of Umbraco are you using?
If you're using v4 it's not recommended that you directly access the Member API, instead you should use the ASP.NET Membership module. See this wiki page: http://our.umbraco.org/wiki/how-tos/membership-providers
Unfortunately, I'm using Version3
I've solved it.
After saving all the member properties, and before calling for refreshing the cache, I've called for regenerating the XML content of the member node.
So, I have :
and it is working now
is working on a reply...