2.x Fix a bug when |time_ago didn’t consider timezones correctly
#2758
Conversation
This file contains 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
Update docs with new example
Levdbas
approved these changes
May 31, 2023
Thanks for that, @Levdbas! Well spotted. |
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.
Related:
Issue
The
|time_agofilter doesn’t work correctly when timezone is set to Australia.Solution
strtotime(), but create DateTime objects with their corresponding timezone.{{ post.date }}. It’s important to use a time string including the time.Impact
The
|time_agofilter should work more reliably.Usage Changes
None.
Considerations
None.
Testing
Yes.