Im hooking into the MemberService.Saved event to trigger off some indexing using ElasticSearch whenever a members details are updated via the backoffice or our custom MVC form. I also want to do this when a new member is added.
The problem is that this event seems to be called a lot of different times during; ie during calls to MembershipHelper.Login and MembershipHelper.GetCurrentMemberProfileModel and other operations involving the MemberService. Not sure why the Umbraco core does a save every time a member is accessed but its causing my indexing process to trigger more times than necessary.
Is there a better way of intercepting inserts/updates on members and triggering my indexing process?
Did you get anywhere with this as I am having the same issue in that I am trying to trap when a member is created via the backend however the event you mentioned gets called multiple times as you rightly state.
MemberService.Saved called so many times
Hi
Im hooking into the MemberService.Saved event to trigger off some indexing using ElasticSearch whenever a members details are updated via the backoffice or our custom MVC form. I also want to do this when a new member is added.
The problem is that this event seems to be called a lot of different times during; ie during calls to MembershipHelper.Login and MembershipHelper.GetCurrentMemberProfileModel and other operations involving the MemberService. Not sure why the Umbraco core does a save every time a member is accessed but its causing my indexing process to trigger more times than necessary.
Is there a better way of intercepting inserts/updates on members and triggering my indexing process?
Kind regards
Ben
Hi Ben,
Did you get anywhere with this as I am having the same issue in that I am trying to trap when a member is created via the backend however the event you mentioned gets called multiple times as you rightly state.
Graham
Hi Graham
See this SO thread:
http://stackoverflow.com/questions/24035586/umbraco-memberservice-saved-event-trigger-during-login-and-get-operations
Ben
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.