From 468c281d7d4b7e4ead610f6aa42c8cbe347de489 Mon Sep 17 00:00:00 2001 From: Odie20XX Date: Fri, 31 Oct 2014 15:30:20 +0100 Subject: [PATCH] Update MembershipHelper.cs The parameter "logMemberIn" wasn't used so setting "LoginOnSuccess" on the RegisterModel didn't have any effect. By checking the parameter you can disable automatically logging in the user after registration. If registration failed, it would have returned null in an earlier stage so it's safe to say registration succeeded at this point. --- src/Umbraco.Web/Security/MembershipHelper.cs | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/src/Umbraco.Web/Security/MembershipHelper.cs b/src/Umbraco.Web/Security/MembershipHelper.cs index 737067685b..0faf9a61a3 100644 --- a/src/Umbraco.Web/Security/MembershipHelper.cs +++ b/src/Umbraco.Web/Security/MembershipHelper.cs @@ -172,11 +172,14 @@ namespace Umbraco.Web.Security if (status != MembershipCreateStatus.Success) return null; } - //Set member online - provider.GetUser(model.Username, true); - - //Log them in - FormsAuthentication.SetAuthCookie(membershipUser.UserName, model.CreatePersistentLoginCookie); + if (logMemberIn) + { + //Set member online + provider.GetUser(model.Username, true); + + //Log them in + FormsAuthentication.SetAuthCookie(membershipUser.UserName, model.CreatePersistentLoginCookie); + } return membershipUser; }