Skip to content
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

Improve error message when attempting to edit a deprecated version of a submission #802

Open
lognaturel opened this issue Nov 26, 2024 · 1 comment
Labels
backend Requires a change to the API server

Comments

@lognaturel
Copy link
Member

From @dbemke in #794:

If a user tries to re-submit a submission which was edited in Central there is: “You tried to update a submission, but the copy you were editing (undefined) is now out of date. Please get the new version that has been submitted, and make your edits again.”
errorOutOfDate

This message was designed specifically for the case where there's an attempt to edit a submission version that has been deprecated. This might happen, for example, if you open up two Enketo edit windows from Central, submit one, and then submit the other.

The case in the screenshot above is an attempt to submit the very first submission in an edit chain again after edits have been made. This is happening from Collect where there is no way to get the latest version so the second part of the message isn't helpful.

@lognaturel
Copy link
Member Author

I think the most helpful thing for Central to do would be to accept the submission if the instanceid and submission contents exactly match an existing submission. This would be the same thing that happens if a submission without any following edits is resubmitted.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend Requires a change to the API server
Projects
Status: 🕒 backlog
Development

No branches or pull requests

1 participant