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
There is problem with the connection of sr_feuser_register and commerce mapper.
commerce itself uses the tt_address.name field to store the first name of a person. srfeuser uses the field tt_address.first_name. So in the ext config i defined the mapping first_name:name. The problem is now, when the fe_user gets created, the mapper is triggered to create the tt_address record. This works. But: the first name is never set in the address record. This happens because of BasicDaoParser::parseObjectToModel checks, if there is a method getName() or attribute "name" in the model. AddressDaoObject has both, and so effectively hides the value of "name".
The text was updated successfully, but these errors were encountered:
My "fix" was to remove the local variable and the call to getter function from parseObjectToModel(). It works in my case, but i'm sure, it will break something. But i do not know, why that code is there.
There is problem with the connection of sr_feuser_register and commerce mapper.
commerce itself uses the tt_address.name field to store the first name of a person. srfeuser uses the field tt_address.first_name. So in the ext config i defined the mapping first_name:name. The problem is now, when the fe_user gets created, the mapper is triggered to create the tt_address record. This works. But: the first name is never set in the address record. This happens because of BasicDaoParser::parseObjectToModel checks, if there is a method getName() or attribute "name" in the model. AddressDaoObject has both, and so effectively hides the value of "name".
The text was updated successfully, but these errors were encountered: