8000 [Form][DelegatingValidator] Conflict between a field and collection field with the same name · Issue #1810 · symfony/symfony · GitHub
[go: up one dir, main page]

Skip to content

[Form][DelegatingValidator] Conflict between a field and collection field with the same name #1810

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

Closed
benjamindulau opened this issue Jul 26, 2011 · 7 comments
Labels
Bug Form Good first issue Ideal for your first contribution! (some Symfony experience may be required)
Milestone

Comments

@benjamindulau
Copy link
Contributor

Use case : http://gist.github.com/1106538

When the Entry "title" input value is blank, the form error is rendered next to the title input field of the "specs" field instead of the title one.

In the EntrySpecType, If i change the name of the title field to "whateverisnotitle", everything goes fine, and i assure you i've just changed that ! ;-)

That's a bit inconvenient.

@stof
Copy link
Member
stof commented Apr 4, 2012

@benjamindulau can you check with the master branch ?

@webmozart
Copy link
Contributor

Could you please correct your Gist? There's stuff missing (how does SpecElementType look like?) and I can't reconstruct your problem.

@benjamindulau
Copy link
Contributor Author

@bschussek i've updated the gist. I just tried with Symfony 2.0.12 and the issue is still present.

I'm trying with master branch right now.

edit: added the form template to the gist

@webmozart
Copy link
Contributor

Task for the BHD: Create a failing test case

@pvanliefland
Copy link

Working on this one

@pvanliefland
Copy link

Checked against the master branch with the code in the gist, looks fine to me. I cannot be 100% sure that I reproduced exactly what @benjamindulau as I don't have the controller or the entity code, but I'm positive that the error is associated (and displayed next) to the parent form (Entry) and not in one of the embedded form.

I can provide a test in AbstractLayout, but I am not sure it is necessary.

@webmozart
Copy link
Contributor

Ok. I will close this issue then. Please reopen it if necessary.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Form Good first issue Ideal for your first contribution! (some Symfony experience may be required)
Projects
None yet
Development

No branches or pull requests

4 participants
0