-
-
Notifications
You must be signed in to change notification settings - Fork 240
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
JS broken when LOCALISE_TIMESTAMP set to False #461
Labels
Comments
moment.js should be loaded in any case to get proper formatting of the data:
So to get a nice formatting, just without TZ conversion, in timestamps.js you can just remove the line: to get the data in utc, so something like:
|
gdubicki
added a commit
that referenced
this issue
Oct 23, 2022
gdubicki
added a commit
that referenced
this issue
Oct 24, 2022
@gdubicki Thanks for the follow up. |
gdubicki
added a commit
that referenced
this issue
Nov 21, 2022
Fix released in v4.2.1 today. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In _macros.html#L71 there is a call to
localise_timestamp()
that is done independently of theLOCALISE_TIMESTAMP
setting. WhenLOCALISE_TIMESTAMP
is set toFalse
,moment.js
is not loaded at all (seelayout.html
) resulting in JS errors:Ideally even when
LOCALISE_TIMESTAMP
is set toFalse
the timestamps should be properly formatted in a nice way, just preserving the original times without TZ conversion.As a side note the
README
is a bit confusing regarding this option given that it states:While it seems to me that it normalize it to the client's time when set to
True
.The text was updated successfully, but these errors were encountered: