Sorry to reopen this issue.
But we are facing the same problem in Central 2025.2.2 with the following form without any search() call
Fields remain empty where they were filled before.
orthopteroides.xlsx (702,8 Ko)
Sorry to reopen this issue.
But we are facing the same problem in Central 2025.2.2 with the following form without any search() call
Fields remain empty where they were filled before.
orthopteroides.xlsx (702,8 Ko)
There are actually two problems with the webform, probably connected:
After the last Central update, the existing access link for this webform opened a "connexion” page to Central so I had to generate a new access link and that’s with this new link that we found out this issue.
So sorry you’re running into issues @mathieubossaert and @nathalie_H! Am I understanding correctly that this is NOT an issue with ODK Collect but with a form that you are filling out on the web? Assuming that’s right, I’ve split this off into its own thread.
Can you say more about this? Are you saying that you expect to have a chance to fill out the form again but instead can’t?
This is highly unexpected. And when you logged in did it show the correct form or not?
I think @Sadiq_Khoja is the best positioned to dig in deeper here.
I’m sorry I read the first thread to fast… Yes we are having the problem with enketo. I changed the title of this thread to be more precise.
Yes. It’s a form that people need to fill out several times, but when they click on the submission button, they get a message of “thank-you-and-you-can-close-the-page”. Just as a one-shot submission link, they have to close the page and click again on the access link to fill out a new form.
I didn’t try because when my colleagues brought that to my attention, I just tried to find a quick answer for them not to be stucked and they haven’t any account to Central. I remembered Mathieu had updated Central a few days ago and thought it may have changed some things.
So I generated a new link, which seemed OK (as they could access again to the webform without log in to Central) until they told me about the unique submission trouble.
Hi @nathalie_H and @mathieubossaert,
I was able to look into this and found out that by default last-saved
instance was not supported with the public access links even in the previous versions of Central. One had to remove single
from the URL to get that working. Can you please confirm that you used to remove single
part of the URL before sharing?
Regarding the previous URL not working, not sure why that’s not working. Do you have the link? What happens when you access the link? Is it revoked in the Central?
Hi @Sadiq_Khoja,
Sorry, I forgot an important part of the informations : yes, I removed “single” in the first url, and it worked well with last-saved.
When I generated the new link, there wasn’t any “single” written in the url but as I were asked to check a box if it was for unique submission (and I didn’t check it), I supposed it was taken into account.
I was answering “no” because I could only see the new one in Central, but I decided to look into the emails I sent last year to my colleague and found it… And I’ll try to make it short for you.
At first, I was very confuse because I couldn’t see any difference between the two url, except for their “behaviour”.
I tested the first one and it opened the webform with las-saved values. As I was connected to Central at this moment, I logged out and re-clicked on it and, this time, got a connection page. I logged in and got the webform page with last-saved values.
I tried the “new” one and it opened a blank webform page.
At the end, looking more closely at both urls, letter by letter, I’ve found the difference: after our Central server’s url, there is “/-/” in the first link (the one from wich I removed the word “single”) and “/f/” in the most recent one.
Here are both links:
It may be not obvious at first sight but I spared you some episodes of the serial.
Thank you very much for your patience.