-
Notifications
You must be signed in to change notification settings - Fork 347
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
duplicate collection index if you delete an item and then add a new one #1106
Comments
One solution would be the ability to set the initial_size variable via a data attribute on the widget in php ....
$builder->add(
'nice_email_collection_with_options',
'collection',
array(
'type' => 'email',
'attr' => array('data-collection-initial-size' => 3),
.... then using it in the collection plugin definition $.fn.collection = function (option) {
var coll_args = arguments;
...
if($(collection_id).data('collection-initial-size')){
options.initial_size = $(collection_id).data('collection-initial-size');
} |
Why is this still a problem? Are there any workarounds for this? |
I assume because nobody has fixed it yet |
MisatoTremor
added a commit
to MisatoTremor/MopaBootstrapBundle
that referenced
this issue
Jan 22, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When using the collection widget, with the mopaboostrap-collection.js you can end up with duplicate indexes which results in either errors when processing the form values, or data going missing.
Easy to reproduce:
You will see that the second and newly created third item will have the same index of [2].
They only way to use the widget in it's current form is to add all the new items you need, and then delete the ones you don't just before saving
The text was updated successfully, but these errors were encountered: