-
-
Notifications
You must be signed in to change notification settings - Fork 30
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
Issue During Questionnaire Submission #168
Comments
I will investigate if this is a general issue. Have you published the form or is it in draft mode? |
Thank you very much for your research. It is a published form. |
@pliciwebstephane I tried to reproduce it, but haven't had success. would it be possible to get an export of your form structure: It might help to see if it is related to a specific setup you have in your form. Also have you tried to create a second form, and does it have the same behavior? |
With pleasure, is there a way to send it to you privately? |
i send you a mail. |
Thanks for that! Can you also tell me what version you are using right now? Is it the latest release? |
Ok, from your import, I can see that you are probably not on the latest version right now. It would be very nice if you could upgrade to https://github.com/deck9/input/releases/tag/v1.9.2 and then send me again a new export. Unfortunately all versions before that had a bug regarding the export of forms containing groups. Sry for that! |
i changed my dockerimage from ghcr.io/deck9/input:main to ghcr.io/deck9/input:v1.9.2 |
ok, i will try to work with the import you send me and then send you a fresh import.json that you can use to restore your form. |
ok it is ok it is my app_url the problem |
Now, my form is ready again. |
i will test it |
We created a form and are using "input" under Docker.
During the submission of the form, at the final step, it fails.
We have an XHR request that returns a 404 error.
https://yyyyyyyyyyyy/api/public/forms/jY85
Response:
{
"message": "No query results for model [App\Models\FormBlockInteraction]."
}
No more log seems available.
The text was updated successfully, but these errors were encountered: