yv01p/Umbraco-CMS
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Comments out backported code - need to wait till we merge in the custom membership branch.

Browse Source
This commit is contained in:
Shannon
2013-11-20 17:10:15 +11:00
parent b13c3aa3b9
commit 416a9ed064
1 changed files with 28 additions and 26 deletions
Download Patch File Download Diff File Expand all files Collapse all files

54
src/umbraco.providers/members/MembersMembershipProvider.cs
View File

@@ -1029,31 +1029,33 @@ namespace umbraco.providers.members
#endregion
}
/// <summary>
/// Adds some event handling
/// </summary>
public class MembershipEventHandler : ApplicationEventHandler
{
protected override void ApplicationStarted(UmbracoApplicationBase umbracoApplication, ApplicationContext applicationContext)
{
Member.New += Member_New;
}
//TODO: We need to re-enable this in 6.2, but need to back port most of the membership provider changes (still in a custom branch atm)
void Member_New(Member sender, NewEventArgs e)
{
//This is a bit of a hack to ensure that the member is approved when created since many people will be using
// this old api to create members on the front-end and they need to be approved - which is based on whether or not
// the Umbraco membership provider is configured.
var provider = Membership.Provider as UmbracoMembershipProvider;
if (provider != null)
{
var approvedField = provider.ApprovedPropertyTypeAlias;
var property = sender.getProperty(approvedField);
if (property != null)
{
property.Value = 1;
}
}
}
}
///// <summary>
///// Adds some event handling
///// </summary>
//public class MembershipEventHandler : ApplicationEventHandler
//{
// protected override void ApplicationStarted(UmbracoApplicationBase umbracoApplication, ApplicationContext applicationContext)
// {
// Member.New += Member_New;
// }
// void Member_New(Member sender, NewEventArgs e)
// {
// //This is a bit of a hack to ensure that the member is approved when created since many people will be using
// // this old api to create members on the front-end and they need to be approved - which is based on whether or not
// // the Umbraco membership provider is configured.
// var provider = Membership.Provider as UmbracoMembershipProvider;
// if (provider != null)
// {
// var approvedField = provider.ApprovedPropertyTypeAlias;
// var property = sender.getProperty(approvedField);
// if (property != null)
// {
// property.Value = 1;
// }
// }
// }
//}
}