I have found it very difficult to extend the default User class in OroUserBundle. I am aware I could easily create a new user class and alter the parameters in config.yml to point to my new class. However, it seems to me that I would also have to rewrite alot of the other classes in the User bundle to make that work.
I would like to introduce my own entity as an association in the user class with the user being the owning side. Is there an easier way to do this?
In my opinion, defining OroUserBundle:User as @MappedSuperclass would help a lot for those intending to have their own implementations and not lose alot of the existing functionality. Possibly true for many of the other entities defined in the OroPlatform.
Keep up the good work.
You must be logged in to reply to this topic.