-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Export: Allow multiple simultaneous exports from a site #87
Milestone
Comments
This issue has been marked as stale because it hasn't been updated in a while. It will be closed in a week. If you would like it to remain open, can you please comment below and see what you can do to get things moving with this issue? Thanks! 🙏 |
This was referenced Jul 10, 2020
This was referenced Aug 17, 2020
This was referenced Aug 28, 2020
This was referenced Oct 20, 2020
This was referenced Sep 12, 2021
This was referenced Nov 28, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We made a decision at one point to prevent multiple simultaneous exports, but that shouldn't be necessary. That said, if it's a real pain to allow simultaneous exports (from multiple sites as you switch around within the app, for example), we should think more about the best user experience.
If exports will rely on an async process and trigger a notification or other 'offline' alert, it seems fine to allow multiple exports. We don't have a great way to show progress, so the best we could do (if we prevent multiple simultaneous exports) is to disable the whole page and sort of just make people wait, which doesn't feel like a great experience.
We could trigger a global notice that looks like:
When finished it could fire off a success notice, and a notification that contains the link to download the export file, and an email saying the same.
If you trigger multiple exports you would have more than one 'exporting' notice stack up.
The text was updated successfully, but these errors were encountered: