You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Dear support,
we met a problem with the field mapping of the gender attribute to Magento.
When a customer logs in, even if the values get correctly modified into Observer/DefaultCMSSyncFieldMapping.php ,
switch ($gigyaProfile->getGender()) {
case 'm':
$customer->setGender('1');
break;
case 'f':
$customer->setGender('2');
break;
default:
$customer->setGender('3');
}
the value that gets saved into Magento is 0.
I found out that in Model/MagentoCustomerFieldsUpdater.php the method setAccountValues(), even if the correct account with modified values gets passed as a parameter, in the following piece of code you take the value from Gigya account
Dear support,
we met a problem with the field mapping of the gender attribute to Magento.
When a customer logs in, even if the values get correctly modified into Observer/DefaultCMSSyncFieldMapping.php ,
the value that gets saved into Magento is 0.
I found out that in Model/MagentoCustomerFieldsUpdater.php the method setAccountValues(), even if the correct account with modified values gets passed as a parameter, in the following piece of code you take the value from Gigya account
to set it later.
In the case of gender attribute this causes the 'm', 'f' or 'u' values to get set into Magento that do not recognize them and sets 0.
The text was updated successfully, but these errors were encountered: