-
-
Notifications
You must be signed in to change notification settings - Fork 5.2k
[Form] Customizing Error Output #3542
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
Comments
Actually it was not a typo but some leftovers from the 2.0. documentation. In Sf 2.0. you used two different blocks for customizing errors: As of Sf 2.1. you use only From the Upgrade 2.1. doc: Before:
After:
|
I wonder why that's not here. Or am I looking in the wrong place? |
By default the errors are rendered in the same way regardless of the fact if it's a field or global error. |
That's right, so adding that (the compound thingy I mean) to the docs is a must have IMHO. |
…rojanowski) This PR was merged into the 2.3 branch. Discussion ---------- Fix the definition of customizing form's global errors. The documentation for customizing global errors was actually still referring to the way it was done in 2.0. (where two different blocks were used: `field_errors` and `form_errors`). Since 2.1. only `form_errors` is used and errors are differentiated using the `compound` variable (set to `true` for form errors). | Q | A | ------------- | --- | Doc fix? | yes | New docs? | no | Applies to | 2.3+ | Fixed tickets | #3542 Commits ------- 6f6fcca Applied some changes according to comments. e3b20d8 Minor rewording. Added tip about meaning of `compound` var and expanded the example code to contain `else` statements. 1e278c4 Added note about customizing errors for different field types. 236d06b Fix the definition of customizing form's global errors.
Looks like there's a typo when explaining how to customize error output for global errors in forms.
In the docs you can read:
and just a few lines below:
Both changes apply to
form_errors
...is that right?The text was updated successfully, but these errors were encountered: