When you use umbracoLastLoginPropertyTypeAlias in the MembershipProvider configuration, to set a property that is automatically updated to the current logindate of a user, it causes the events Member.BeforeSave and Member.AfterSave to fire.
Thus, be careful when you use these events, don't do anything heavy in them.
Oh, and does anyone know of a graceful way to handle this? And, should this be logged as a bug, or maybe it's an intended "feature"?
Using umbracoLastLoginPropertyTypeAlias causes Member events Beforesave and AfterSave to be fired on every login
Todays gotcha:
When you use umbracoLastLoginPropertyTypeAlias in the MembershipProvider configuration, to set a property that is automatically updated to the current logindate of a user, it causes the events Member.BeforeSave and Member.AfterSave to fire.
Thus, be careful when you use these events, don't do anything heavy in them.
Oh, and does anyone know of a graceful way to handle this? And, should this be logged as a bug, or maybe it's an intended "feature"?
is working on a reply...