I'm creating new PHPOpenChat users through a separate form on my site, using
the same MySQL statements as are in the class.Chatter.inc "register"
function. Seems pretty straightforward -- add a username, password, and
confirm code to "poc_user_account" and add a nick, user, name, email,
picture, and regtime to "poc_user_data".
I'm able to create the records of course, but the accounts cannot login to
the chat system. It kicks back to the login page with no error message (why
are there no error messages?). Is there something I'm missing that
PHPOpenChat needs to authenticate a user? Is there a way to turn on verbose errors / debug code / etc.?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2004-01-22
Turns out I had the "SEND_CONFIRMATION_MAIL" configuration option turned on (in config.inc.php). The login function, called "is_authorized," will fail if this confirmation mail option is true AND the user's "CONFIRM_CODE" is not null.
The fix was to either clear the confirm code when authorization was made by an admin, or to set "SEND_CONFIRMATION_MAIL" to false.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm creating new PHPOpenChat users through a separate form on my site, using
the same MySQL statements as are in the class.Chatter.inc "register"
function. Seems pretty straightforward -- add a username, password, and
confirm code to "poc_user_account" and add a nick, user, name, email,
picture, and regtime to "poc_user_data".
I'm able to create the records of course, but the accounts cannot login to
the chat system. It kicks back to the login page with no error message (why
are there no error messages?). Is there something I'm missing that
PHPOpenChat needs to authenticate a user? Is there a way to turn on verbose errors / debug code / etc.?
Turns out I had the "SEND_CONFIRMATION_MAIL" configuration option turned on (in config.inc.php). The login function, called "is_authorized," will fail if this confirmation mail option is true AND the user's "CONFIRM_CODE" is not null.
The fix was to either clear the confirm code when authorization was made by an admin, or to set "SEND_CONFIRMATION_MAIL" to false.