CB

When activateUser is called and the user is confirmed and approved it sets block to 0 and causes a user store that doesn't fire an update event. This causes problems for registrations that are already confirmed and approved breaking changes to users made during the new registration triggers to be lost if not done on the user object by reference. It'll do that store even though it's entirely unnecessary. That store should check if block is == 1 before bothering to set it to 0 as if it's already 0 there's no reason to store.