Hi everyone, A user is reporting issues when creating a CSV list for downloading. Previous to v7.9.3 the user could perform the process with a notification being presented shortly after for download. After upgrading to V7.9.3 it seems we need to:
Perform the task to create the CSV list
Log out of Specify and back in
Click on the notifications tab and download the CSV list
I am unable to replicate this in v7.9.3.1. Have you been able to recreate the user’s issue?
Instead of logging out and back in, have you tried navigating elsewhere in Specify after starting the export? It’s possible that the CSV export is taking a while. Logging out and back in may have allowed it time to complete.
I updated our instance from v7.9.3 to v7.9.3.1 and was able to recreate the issue on my end.
Log in as a user
Click on Query > Run a query > Click on “Create CSV”
Message pops up “Export File Being Created”
I navigated to Attachments; Statistics and also run another query and the notifications tab did not update.
By changing the Collection on the lower left hand side, causes the page to refresh, and the Notifications tab now reflects the Query exports are completed and ready to download.
I did wait a few minutes between running queries, but only when doing the above or signing out and back in, resulted in the Notifications tab being updated
I believe I may have been able to recreate the issue, although inconsistently.
Can you share your Specify 7 System Information with me so I can try using the same browser and system configuration as you?
Same here. Running just-specify7 docker-compose tag v7.9. Tried with Firefox 130, Microsoft Edge and Duckduckgo Browser on Android mobile phone, all three with same behavior:
Create and run a (small) query
Click on ‘Export to CSV’
Dialog ‘Export File Being Created’
Notification is never triggered, unless I either switch Collection or log out and in again.
Side note: notification time seem to be expressed in UTC because I never get a ‘Now’ tag, always ‘2 hours ago’ and I am on CEST time zone (UTC +2)
I have added your report to the GitHub issue tracking this!
This is because the back-end of Specify does not support time zones (#641), but we are aware of the oddness and do have an open ticket for this as well.