[6.x] Fix range date fields not updating with configured timezone#14984
Open
lazerg wants to merge 1 commit into
Open
[6.x] Fix range date fields not updating with configured timezone#14984lazerg wants to merge 1 commit into
lazerg wants to merge 1 commit into
Conversation
lazerg
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Range date fields with a configured timezone (not 'auto') were not correctly converting the user's input from the field's timezone to the app timezone before saving.
The
processDateTimemethod now uses the field's resolved timezone when parsing datetime values, ensuring dates are properly converted when a specific timezone is configured.Fixes #14636