I sounds like eZp 4.2 could simplify this process for everyone at once. http://issues.ez.no/14882
I would actually apply the patch and proceed with local development in preparation for and using the workflow event / trigger system to complete tasks like these.
You can also do custom user activation in 4.1 and up. See [UserSettings]VerifyUserType for how to setup custom account activation handlers, same can be done with RegistrationFeedback.
This was added to be able to support activation through sms for instance, but you can pretty much do whatever you want in them. Just remember to handle the user activation correctly (see default email code).
Thank you guys for you kind help. Much appreciated...
@Heat - I am using 4.0.1, is it possible to apply the patch to the version I am using. Can you please explain the suggested process in bit more detail.
@Andre - gone through the code which you mentioned.
else if ( $verifyUserType )// custom account activation
{
$verifyUserTypeClass = false;
// load custom verify user settings
if ( $ini->hasGroup( 'VerifyUserType_' . $verifyUserType ) )
{
if ( $ini->hasVariable( 'VerifyUserType_' . $verifyUserType, 'File' ) )
include_once( $ini->variable( 'VerifyUserType_' . $verifyUserType, 'File' ) );
$verifyUserTypeClass = $ini->variable( 'VerifyUserType_' . $verifyUserType, 'Class' );
}
// try to call the verify user class with function verifyUser
if ( $verifyUserTypeClass && method_exists( $verifyUserTypeClass, 'verifyUser' ) )
$sendUserMail = call_user_func( array( $verifyUserTypeClass, 'verifyUser' ), $user, $tpl );
else
eZDebug::writeWarning( "Unknown VerifyUserType '$verifyUserType'", 'user/register' );
}
I am totally confused. It would be appreciated if you can explain in bit more depth.
You must be logged in to post messages in this topic!
