Fix timezone shift in search when using date-only input#841
Open
NativoDigital wants to merge 1 commit intoOctopoos:masterfrom
Open
Fix timezone shift in search when using date-only input#841NativoDigital wants to merge 1 commit intoOctopoos:masterfrom
NativoDigital wants to merge 1 commit intoOctopoos:masterfrom
Conversation
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
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.
This pull request addresses the issue described in Issue #679, where the
calendarfield in search mode returns results from the previous day when Joomla is configured with a timezone other than UTC.Bug: calendar search field returns previous day when Joomla timezone ≠ UTC
When using the
calendarfield in search mode (onCCK_FieldPrepareSearch), and Joomla is configured with a timezone like GMT+2, searching for a specific date (e.g.2025-05-27) returns items from the previous day.This is due to the fact that date-only inputs (e.g.
2025-05-27) are interpreted as midnight in the local timezone (2025-05-27 00:00:00), and then converted to UTC (2025-05-26 22:00:00), which shifts the intended search range.Solution
The fix adds a check to detect whether the input date string includes a time component. If not, it appends
12:00:00before the conversion to UTC. This avoids the unintended shift to the previous day.Added in
onCCK_FieldPrepareSearch():Scope
Thanks for maintaining Seblod. I hope this small fix will help others experiencing this issue.