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

Calendar crash with "date" (not datetime) field as date_begin / date_end #12956

Closed
adrianofoschi opened this issue Apr 22, 2022 · 1 comment · Fixed by #12957
Closed

Calendar crash with "date" (not datetime) field as date_begin / date_end #12956

adrianofoschi opened this issue Apr 22, 2022 · 1 comment · Fixed by #12957
Labels

Comments

@adrianofoschi
Copy link

adrianofoschi commented Apr 22, 2022

Describe the Bug

If you choose a "Calendar Layout" option and you set a "date" field as date_begin or date_end it crashes.

To Reproduce

  • Create a collection "mycollection"
  • Add a "DATE" (not datetime, only date) field "mydate"
  • Open collection "mycollection" in table layout
  • Create a new item "myitem"
  • Switch from table layout to calendar layout
  • Set date_begin and date_end time on "mydate"

Errors Shown

In browser console: RangeError: Invalid time value

What version of Directus are you using?

9.9.0

What version of Node.js are you using?

16.14.2

What database are you using?

Postgres 13

What browser are you using?

Firefox

How are you deploying Directus?

docker-compose

@azrikahar
Copy link
Contributor

Thanks for the update. Seems like making sure it's a Date field was the missing key in #12871 (but you did update there as well!) 👍

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 2, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants