You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 16, 2022. It is now read-only.
I am using the Daniel-KM Fork of NeatlineTime. When I add an item to my timeline, unless the date values for my items follows the YYYY-MM-DD format, one the timeline the date appear as January 1, 1970. So for instance, if I have the date value equal 2012-02-01, it works fine, but if I have the date value equal February 1, 2012, then my timeline will display the date as January 1, 1970.
In the documentation it says that example date values we can use are:
January 1, 2012
2012-01-01
1 Jan 2012
2012-12-15
but since not all of these work I thought I'd report this problem as an issue here.
Thanks.
The text was updated successfully, but these errors were encountered:
The documentation may be not up to date, or the feature may be missing.
Anyway, the date depends on many things, in particular the locale of the server, the locale of Apache, the locale of Php, and many other things. The better is to manage date as pure iso in metadata, so they will be more maintainable and more shareable in the long term. Then, the theme can apply a localization of the date.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
I am using the Daniel-KM Fork of NeatlineTime. When I add an item to my timeline, unless the date values for my items follows the YYYY-MM-DD format, one the timeline the date appear as January 1, 1970. So for instance, if I have the date value equal 2012-02-01, it works fine, but if I have the date value equal February 1, 2012, then my timeline will display the date as January 1, 1970.
In the documentation it says that example date values we can use are:
January 1, 2012
2012-01-01
1 Jan 2012
2012-12-15
but since not all of these work I thought I'd report this problem as an issue here.
Thanks.
The text was updated successfully, but these errors were encountered: