-
Notifications
You must be signed in to change notification settings - Fork 6
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
Validation for multiple sections doesn't work #8
Comments
Perhaps it's related to #7. I'll re-re-fix it and please check again this one. |
Ok, now I understood what you're saying. I pushed some local XSLT fixes to version 2.3.2.
The idea behind
The idea behind If you want to display a consolidated message for all entries, gather all interpretations from all entries and manually write some code to display appropriate message.
These are the processing stages. All entries go through each stage simultaneously:
In your case, Entry#1 passed Stage#4 but Entry#2 didn't. The success message is applied to an Entry only if it passes Stage#7. An appropriate error message is applied to an Entry whenever it fails at one stage. If any entry fails at any stage, processing is stopped after that stage is completed and current status is returned. |
Thanks for the clarification. The fields for the multiple entries I'm creating are actually being inserted via javascript, so if I'll check out the updated utilities to see if it addresses the blank divs issue! |
It won't :)
No. It's soul job is to render one entry. If you need to render all entries in given wrapper or something, then ... do it. Of course there is room for improvement: another |
Alright thanks for your thoughts! |
I'm not sure what the exact problem is, but here's what's going on:
I have something like this
I basically have posts with images. The upload field in the images field has a validation to only allow image files. If I try to upload a PDF, I get two empty success divs:
But the event XML is showing this:
In the images section:
Problems:
The text was updated successfully, but these errors were encountered: