Notifications
I have created a new module that adds phone verification step to the signup process. The problem I have is that I cannot update the users table after the signup process with the phone number received. I tried registering a hook in application/modules/mymodule/settings/manifest.php as follows:
'hooks' => array(
array(
'event' => 'onUserCreateAfter',
'resource' => 'User_Plugin_Phone',
),
),
Then, I created the class User_Plugin_Phone in application/modules/User/Plugin/Phone.php as follows:
class User_Plugin_Phone extends Core_Plugin_Abstract {
public function onUserCreateAfter($event) {
echo 'console.log("Inside User_Plugin_Phone::onUserCreateAfter");';
echo 'alert("Inside User_Plugin_Phone: onUserCreateAfter");';
$payload = $event->getPayload();
}
}
But the hook is never triggered after signup completes. Tried many times. Any ideas will be appreciated.
Please remember what we said in the last thread about code. Your code is not in tags. Normally, we delete as per our posted rules. Please edit your post.
Hi Donna. Fixed that. Thanks
Are you trying with a standard Profile Question for the phone number? If not, perhaps try that as it already has the routine to save to db and would take less code since that process is already there.
No, I have added a new step and even created its admin form. The problem is I don't know how to update the users table with the phone number I have received from the user in my new signup process. I tried that in the onSubmit() method of the new class, but in that stage, the viewer has always an identity of 0 and I cannot update it.
Engine_Api::_()->user()->getViewer()->getIdentity(); Not sure why you don't want to try the default Profile Questions and then tie your plugin into that question. Grab it and use it. Other than re-creating the wheel.
I am not sure if that will work for me. Actually, I will need to get the phone number, which I can do now, no problem. But, I have problem saving the number at the end of the registration. It's not clear which methods in which classes are invoked after registration is done.
Further, my module will need to serve my mobile app too, serving as a small REST API too.