[SOLVED] In Auto Actions, is onAfterNewUser the Right Event?

Turns out this weird behavior I reported has to do with how I've been testing my code. I would first register the new user ONE TIME, but then after that, to repeatedly generate the aforementioned sequence of events, I would just set both Confirmed and Approved to No in the site back end user profile and then click the confirmation email link and re-approve the user in the front end. Apparently, this is NOT equivalent to starting all over with a new registration request since, when I do that, my update query works and the profile field values stick.

So this is an interesting thing to note when testing these events both in CB Auto-Actions and also in custom plugins. Now I know.

For that you'd need to also act on onAfterUserApproval, but that trigger will cause a user ->store if the user account is blocked (should be unconfirmed, unapproved, and blocked to mimic new registration state). The user store would cause your changes in a direct database query to be lost unless the user object is also updated (which a field action does). The user object is the first variable of that trigger so your custom plugin just needs to be sure to also set the new value in the user object in addition to the query. Alternatively you can act on onUserActive which is fired after the user store caused by the above situation.

BINGO!

The onUserActive event was exactly what I was looking for! This actually eliminates the need to have individual trigger registrations and methods in my plugin for each of onAfterUserRegistration, onAfterUserConfirm, and onAfterUserApproval triggers and having to check how user registration is configured in each of those methods. This single trigger seems to fire at the end of that sequence no matter how it is configured in CB Configuration.

THANK YOU VERY MUCH, KYLE! You are awesome!

Bruce