Bug description
Dates set to the range UI mode in a blueprint with a timezone specified do not properly update when saved on entries.
How to reproduce
Create a blueprint with a date using the range UI mode and assigned to a timezone other than the native system timezone (I uses "America/New_York", for example).
Create a new entry using the blueprint, include a date range for the date field. Save the entry.
Now try to change the date range and save the entry again. You will see that what is saved is not what you entered. Among the errors I've observed:
- changing the hour on the start and end times does not work, the times are reverted when saved
- changing the day-of-month get saved, but the hour is incremented by one as a side effect
Environment
Environment
Laravel Version: 13.6.0
PHP Version: 8.3.30
Composer Version: 2.9.5
Environment: local
Debug Mode: ENABLED
Maintenance Mode: OFF
Timezone: UTC
Locale: en
Cache
Config: NOT CACHED
Events: NOT CACHED
Routes: NOT CACHED
Views: CACHED
Drivers
Broadcasting: log
Cache: file
Database: sqlite
Logs: stack / single
Mail: log
Queue: sync
Session: file
Storage
public/storage: NOT LINKED
Statamic
Addons: 1
License Key: Not set
Sites: 1
Stache Watcher: Enabled (auto)
Static Caching: Disabled
Version: 6.17.0 PRO
Statamic Addons
tenseg/zone-date: dev-main
Installation
Fresh statamic/statamic site via CLI
Additional details
I have captured a video of the bug in action.
The "Zone Date" in the video is my work-in-progress field, which you can ignore. The "Range Date" is a standard Statamic date using the range UI. The "Single Date" is a standard single UI Statamic date, which does not seem to exhibit the same saving problem.
Bug description
Dates set to the range UI mode in a blueprint with a timezone specified do not properly update when saved on entries.
How to reproduce
Create a blueprint with a date using the range UI mode and assigned to a timezone other than the native system timezone (I uses "America/New_York", for example).
Create a new entry using the blueprint, include a date range for the date field. Save the entry.
Now try to change the date range and save the entry again. You will see that what is saved is not what you entered. Among the errors I've observed:
Environment
Installation
Fresh statamic/statamic site via CLI
Additional details
I have captured a video of the bug in action.
The "Zone Date" in the video is my work-in-progress field, which you can ignore. The "Range Date" is a standard Statamic date using the range UI. The "Single Date" is a standard single UI Statamic date, which does not seem to exhibit the same saving problem.