Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem with tt_address.name and AddressDAO #132

Open
sir-gawain opened this issue Aug 23, 2016 · 2 comments
Open

Problem with tt_address.name and AddressDAO #132

sir-gawain opened this issue Aug 23, 2016 · 2 comments

Comments

@sir-gawain
Copy link

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".

@garbast
Copy link
Contributor

garbast commented Aug 23, 2016

Feel free to submit a pull request with a fix.

@sir-gawain
Copy link
Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants