Closed jcrombez closed 11 years ago
Hi,
Did you figured out ? I have got exactly the same issue...
Hi,
I was on holidays last week, i'll try to look at it this week.
Thank you for this fix.
Just a little thing : when adding file programmaticly, i have to specify createdAt manually. Not a big deal but, it would be nice to keep that on the bundle side.
Yes I know for the create at. It's a 'wanted' behaviour as long as I don't want to force a dependancy with a lib like gedmo doctrine extensions.
A simple default value in the constructor would do the job, do you see any problem with this solution ?
You are right. waiting for your PR :)
My fork has a composer set for SF 2.2, is it okay ?
Did not tested yet, you can try to run tests and see.
Well actually, the BaseFile is an abstract class, and so if we setup constructor, children must call the parent constructor to achieve the initialization.
So .. I think it's better for you to just setup the constructor in your children class.
What's the problem with calling the parent constructor when a children constructor is needed ?
I'm trying to programmatically create a new user with its avatar.
I'm basically doing this :
But then i got the following Exception :
I have no problem defining an avatar through the profile form on a classically registred user.