Please Log in or Create an account to join the conversation.
onAfterUserRegistration is the correct trigger. It fires directly after the user object is stored successfully. It however only applies to frontend so if you're creating users from backend you need to use onAfterNewUser. Do you have a redirect action acting on or before that trigger that maybe could be interrupting your query action?We need to update a DB table during the registration process, before any CBsubs trigger and it seems that onAfterUserRegistration does not update the table.
Your condition is likely what is failing. If you're checking if the value is null it's just checking if the field is equal to the string null. Use a "Is Empty" or "Is Not Empty" condition.We would like to update the AffiliateTracker table just after the user has been saved by CB in order to reflect any affiliate parent id and use the following request auto action with a condition of [cb_codeatid] field not null
Please Log in or Create an account to join the conversation.
Use a "Is Empty" or "Is Not Empty" condition.
No we don't have any redirects.Do you have a redirect action acting on or before that trigger that maybe could be interrupting your query action?
Please Log in or Create an account to join the conversation.
Yes, but if it's integer it's usually best to just check that its value is greater than 0.This is an integer number field, so it may be equal to zero, in this case will empty still works ?
Does the field you're conditioning against exist during registration and is accessible to the user? Beyond that I've no idea. You're using the correct trigger. Enable debug mode and maximum error reporting in Joomla global configuration then enable debugging for the auto action within its parameters. That should output any errors it may have including if a condition fails and what values it saw.What is strange is that if I use onAfterFirstLogin to test, the auto action fires successfully
Please Log in or Create an account to join the conversation.
Yes the field is even validated by a query at registration to check it's ok and existing.Does the field you're conditioning against exist during registration and is accessible to the user?
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.