Open Bubelbub opened 8 years ago
I have the same issue after migrating to Symfony 3.1 . Any fixes?
Try with entry_type
instead of type
.
entry_type was introduced with 2.8 to replace type.
Also options
should be replaced by entry_options
Here you can find all the important changes: https://github.com/symfony/symfony/blob/master/UPGRADE-3.0.md
I also get deprication warnings even if I use entry_type
.The BootstrapCollectionType
still uses it too I believe. This needs to be fixed too. Correct me if I am wrong, but I think if it isn't, you would need to specify the type everytime after symfony 3.0. Even for text
types as that is defined as default in the BootstrapCollectionType
.
Hey guys,
I'm risking the use of the new Symfony 3.1 with this not 100% compatible BraincraftedBootstrapBundle :+1: Normally everything works really really great! :tada:
But I have a problem with collections and it seems like that the
type
is ignored.Example form
RecipeType
:And then I have this type
RecipeIngredientType
:The error message:
My idea:
If I check the line 15 (not 52) I see this:
And the system shows the same error message all the time. With "type" attribute and without. - Always the same error. The system is using this simple field - but it is a collection...
So maybe you can give me more ideas to fix it by myself or maybe you can help by fixing this :+1: Thanks in Advance for anything :+1: