Updated Joomla user e-mail address not updating Hikashop for checkout

Hi,

There was never a synchronization added to update the email address in HikaShop when the email is changed from the CB interface.
Try adding the code:

public function onAfterUserProfileSaved(&$user, $env) {
		if(empty($user->id) || empty($user->email))
			return;
		if(!defined('DS'))
			define('DS', DIRECTORY_SEPARATOR);
		if(!include_once(rtrim(JPATH_ADMINISTRATOR,DS).DS.'components'.DS.'com_hikashop'.DS.'helpers'.DS.'helper.php'))
			return true;
		$userClass = hikashop_get('class.user');
		$hikaUser = new stdClass();
		$hikaUser->user_email = $user->email;
		$hikaUser->user_cms_id = $user->id;
		$userClass->save($hikaUser, true);
	}

Hi,

1. I'm not sure what you mean here.
This new function updates the email address in HikaShop's user entry when it is updated in CB.

2. Normally, the link to the profile edition page from the user control panel of HikaShop is the Joomla profile edition page. And yes, if you change the email address in the Joomla profile edition page, it is updated in HikaShop as HikaShop implements the standard Joomla user triggers to pick up on such modifications.
However, if CB overrides that Joomla profile edition page with its own page, which doesn't trigger the standard Joomla triggers when a user information is modified, then the email address won't be updated in HikaShop. And in such case, I suppose this new function should fix that.
CB not triggering the standard Joomla user triggers when the user information is updated and not registering the Joomla user triggers so that it can update itself when the Joomla user information is changed from elsewhere has always been a problem.
We already have several patches in the code of HikaShop specific to CB (like for example during the user registration in HikaShop).
Ideally, extensions should only have have to update Joomla's user information and trigger the corresponding triggers so that other extensions could pick up on that by implementing the standard Joomla user triggers (like what HikaShop already does).
The way it's done in CB, any extension that has to touch the Joomla user information has to implement code specific to CB to keep the synchronization or that extension can't work properly with CB on the same website.

Hi,

I suppose the issue is a timing and synchronization issue.
Without implementing the new code/function, HikaShop is not notified that the user changed his email address in CB.
However, CB does update the Joomla user entry.
Then, when the user arrives on a page of HikaShop, HikaShop doesn't see any entry corresponding to the email address of the current Joomla user and thus creates a new one.
With the new code/function, the user entry will be updated in HikaShop, so that new entry won't be created in HikaShop afterwards as HikaShop will already see the modified entry matching with the current Joomla user.

Hi,

Thank you for your feedback.
We'll add that change on our end for the next version of HikaShop so you won't have to redo it next time you update your HikaShop.