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

Can't Save Collection Update Because of Date Format Issue #1875

Closed
mf795 opened this issue Jul 21, 2022 · 2 comments · Fixed by #1889
Closed

Can't Save Collection Update Because of Date Format Issue #1875

mf795 opened this issue Jul 21, 2022 · 2 comments · Fixed by #1889
Labels
1 - Bug Incorrect behavior of the product

Comments

@mf795
Copy link

mf795 commented Jul 21, 2022

Describe the bug
With the new version, my Specify switched my date format to MM/DD/YYYY and I've been trying to find a way to change it to DD/MM/YYYY without switching my computer's settings. From what I did, the blank date box shows that I can put a date in as DD/MM/YYYY, but it won't let me save the collection object unless I change the date to MM/DD/YYYY format. In other words, when I have 20/01/1970 in my date, I can't save, but when I change it to 01/20/1970 I'm given the option to save.

To Reproduce
Steps to reproduce the behavior:

  1. Click username to open settings.
  2. Click preferences
  3. Unselect 'Use accessible full date picker'
  4. Start a new collection object
  5. Blank date box should read 'DD/MM/YYYY'
  6. Add a collection object as normal with dd/mm/yyyy date format and save button will be red and unusable.

Expected behavior
I was hoping that by unselecting 'Use accessible full date picker' I would be able to have the dd/mm/yyyy format for my Specify without changing my computer's settings.

Screenshots
I have the date in dd/mm/yyyy format and the save button is red
image
Changed to mm/dd/yyyy format even though the blank box says I should use dd/mm/yyyy format and save button is orange and clickable.
image

Desktop (please complete the following information):

  • OS: Windows 11
  • Browser: Chrome
  • Specify 7 Version: 7.7.0 (I believe, but I'm not sure how to check)

Reported By
Cornell University

Thank you for your help!

@mf795 mf795 added pri:unknown 1 - Bug Incorrect behavior of the product labels Jul 21, 2022
@maxpatiiuk
Copy link
Member

Thanks for reporting this bug. I was able to reproduce it.

Yes, you are on Specify 7.7.0. But for future reference, to check your version, click on your user name in the top menu, and select "About Specify 7"

For future reference: bug occurred in the day.js library. Present in the newest version of day.js. Added an ugly workaround. Need to consider migrating to date-fns or wait for day.js 2.0

@maxpatiiuk
Copy link
Member

@mf795 Hi. This issue has been fixed.
Change the specify version from 7.7.0 to edge in your docker-compose.yml to get the newest bug fixes.
https://hub.docker.com/r/specifyconsortium/specify7-service/tags?page=1&name=edge

maxpatiiuk added a commit that referenced this issue Jul 28, 2022
Fixes #1908

The fix was applied for PartialDateUi in #1875, but I forgot to also
apply it in other places where date parsing occurs
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1 - Bug Incorrect behavior of the product
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants