-
Notifications
You must be signed in to change notification settings - Fork 623
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 error on custom dropdown fields with special characters #1113
Comments
Same behavior on the GeoAvalanche deployment http://geoavalanche.org/incident @aoduor Might be of help to capture some information more on this? I'm at your disposal, just ask what |
Quick updates on this: GeoAvalanche deployment has 4 custom forms:
I have no ideas what are the differences among them that issue can be related to |
More info about the error:
What I noticed there, is the presence of 2 hidden fields which have both null values: custom_field[2-BLANKHACK] and custom_field[9-BLANKHACK] |
We've got the same problem with a custom form for https://iraqmonitor.crowdmap.com/ It's a private deployment, but happy to give access to people who are looking into resolving this. In the past ten days or so, no reporters have been able to submit a report. Everyone gets the error message described above. I've tried many combinations of responses (no special characters), including leaving all custom fields blank - everything results in an error. We are currently unable to enter reports. This deployment tracks disputes in Iraq, so we are quickly getting a backlog of reports to enter. Any ideas on how quickly this can be resolved? |
Hey @hpuiglarrauri, i'd really appreciate you giving me access to check this out.. Thanks |
Reported by our friends at https://lakatlan.crowdmap.com/, i tested this out locally
The text was updated successfully, but these errors were encountered: