Hi there! I'm seeing some odd behavior occurring with the file uploader component.
One of my clients has built a complex, multi-page form that has many required fields and quite a few conditional ones as well.
In particular, he has a file upload component that is triggered by a conditional field.
If a user lands on this page and does not put any data into the required fields, then clicks the Upload button on the file uploader component (without browsing first), the user is then able to bypass all required fields on the form and move to the next page. Furthermore, if there is data in the fields that precede the file upload component, and the Upload button is pressed without first browsing, all the data in the required fields that precede the uploader is wiped out.
I'm fairly confident that the issue is with the file uploader component because, when the form is filled out like it should be, things work just fine. It only starts to exhibit this odd behavior when the Upload button is pressed without having first browsed for a file.
This is a weird, deep issue that would require a user to do some rather unpredictable things, so I'm not expecting any kind of immediate solution. I would be interested in knowing if anyone else has experienced an issue similar to this, though.
Comments
Comment #1
prl commentedSame issue here, using 7.x-4.0-alpha9. A user can easily bypass the required file upload field by simply selecting "Upload" (without browsing for a file). If I can provide any further troubleshooting assistance, would be happy to help.
Comment #2
quicksketchIt sounds like a JS error might be happening on the page. Clicking the Upload button should not reload the page at all. It should simply do an AJAX request (showing the throbber briefly), and then not do anything at all if a file has not been selected.
I can't reproduce this issue. If steps can be provided to cause the problem, I'll take a look into it.
Comment #3
prl commentedI believe this may be related to #1789040: File upload does not work with conditional rules
Comment #4
charlie charles commentedhttps://drupal.org/project/entityform
Comment #5
quicksketchThank you @charlie charles, that's about as helpful as reporting "use chrome" in a mozilla bug tracker. :P
Comment #6
charlie charles commentedthat might be more suited to entityform as it use the standard drupal fields
Comment #7
charlie charles commentedI hope that helped
Comment #8
danchadwick commentedClosed for lack of activity