Originally Posted by
mc12345678
Can you be more specific about your method of resolving this? From the description I think you did more than was necessary. If what I thought was done, it seems that to provide similar messages and use other information in the future may require far more editing than what is minimally necessary.
I could have also misread the description of how it was resolved.
Thank you for your interest! My solution was to include $messageStack in the notifier call along with other needed data (shown in red):
Code:
$zco_notifier->notify('NOTIFY_PROCESS_3RD_PARTY_LOGINS', $email_address, $password, $loginAuthorized,
$check_customer->fields['customers_member_number'], $check_customer->fields['customers_id'], $messageStack);
and in the observer update function:
Code:
function update(&$class, $eventID, $paramsArray = array(), &$rwParm2, &$loginAuthorized,
&$customers_member_number, &$customers_id, &$messageStack) {
Even though I had to modify the core file to get the data I need into the observer, that change -- add some data to the notifier call -- is better than having all the additional login validation code in the core file. Note: customers_member_number is a store unique variable added to the customers table. Another core file change in the login header file pulls that variable out of the table in the customer query in the file.
I'd certainly be interested in a simpler approach.
Bookmarks