From 2621b25fd34d541fa511cc08b3b1c3aa0d3b8231 Mon Sep 17 00:00:00 2001 From: Shannon Date: Thu, 24 Apr 2014 16:28:37 +1000 Subject: [PATCH] Ensures that member saving events don't get raised for normal member operations like validating and getting a user and flagging them as online. This fixes: U4-3451 Cache on Partial View refreshed, after member execute login --- src/umbraco.providers/members/UmbracoMembershipProvider.cs | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/umbraco.providers/members/UmbracoMembershipProvider.cs b/src/umbraco.providers/members/UmbracoMembershipProvider.cs index f6a5ed6714..dbefa53cc0 100644 --- a/src/umbraco.providers/members/UmbracoMembershipProvider.cs +++ b/src/umbraco.providers/members/UmbracoMembershipProvider.cs @@ -515,7 +515,7 @@ namespace umbraco.providers.members //don't raise events for this! It just sets the member dates, if we do raise events this will // cause all distributed cache to execute - which will clear out some caches we don't want. // http://issues.umbraco.org/issue/U4-3451 - m.Save(); + m.Save(false); } return ConvertToMembershipUser(m); @@ -555,7 +555,7 @@ namespace umbraco.providers.members //don't raise events for this! It just sets the member dates, if we do raise events this will // cause all distributed cache to execute - which will clear out some caches we don't want. // http://issues.umbraco.org/issue/U4-3451 - m.Save(); + m.Save(false); } return ConvertToMembershipUser(m); }