-
Notifications
You must be signed in to change notification settings - Fork 72
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
Enketo submissions don't work for forms with space in formid that are in projects with project-level encryption #364
Comments
i wrote a test that does all of the above except use enketo, and it passes. so it must be something enketo is doing. but i can't debug it without access to that server to see the enketo logs.
|
my best guess enketo is overzealously encoding spaces somewhere? |
@lognaturel does this line mean anything to you? |
and in particular why it differs from line 261 above which references because the instanceID is taken as xml attribute text, i would not expect to see it url-escaped ever. |
Line doesn't mean anything to me but I agree it looks like a very likely culprit. It's definitely something Enketo-specific. I can't see anything obviously related in issues for either enketo-express or enketo-core. I looked at logs and all that's in there since the last restart is From Nothing useful in the redis DB I don't think:
You can I think next steps are to file an Enketo issue and/or try locally. |
i logged on but.. couldn't find where anything is. the thing i would like to see is enketo trying to talk to central, which i don't see in here. (edit: and actually what i'd need to see is the payload of that request which won't be in a log anywhere.) |
There's no logging to that effect other than at the |
Closing in favor of enketo/enketo#1079 since there's no action to take on the Central end. |
+4da6d37bb30dd44716ef68f279669672d279189a server (v1.1.1-138-g4da6d37)
Submission service on data server not found. (404)
I'm pretty sure this is related to the spaces in formid
and that it's a regression. Another interesting thing about this form is that it has a blank version but I've tried another form with a blank version without problem.I get the same behavior with a published form on v1.1.1 but on a draft on v1.1.1 I get a different error message "Unexpected form id value Geotrace_and_shape; did not match the form ID in the URL"
The text was updated successfully, but these errors were encountered: