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
I've read quite a bunch of issues related to date format and some of them relate to the issue I'm having, but I've seen no proper answer to the problem. Please feel welcome to correct me if I'm wrong.
The following date headers will make the post display the appropriate date:
date: 06-01-2022
or
date: "2022-01-06"
but
date: 2022-01-06
won't, it will display today's date instead (or maybe the date the markdown file has been saved).
Seems like a bug to me. But maybe there is an explanation.
It's not a big deal, but not so straightforward to understand why something is not working for users, so may be worth addressing.
Apart from that, thanks a lot for grav, it's amazing :) :) :)
The text was updated successfully, but these errors were encountered:
Thanks for telling me about this workaround @pamtbaau .
Personally, I still think it'd be worth fixing in grav, so that it's more straightforward for users not to encounter this weird behaviour when having/not having quotes. But I don't know how easy it is to fix.
I've read quite a bunch of issues related to date format and some of them relate to the issue I'm having, but I've seen no proper answer to the problem. Please feel welcome to correct me if I'm wrong.
More details on the issue are visible here.
After more investigations, here is the situation:
with the following in
config/system.yaml
:The following date headers will make the post display the appropriate date:
or
but
won't, it will display today's date instead (or maybe the date the markdown file has been saved).
Seems like a bug to me. But maybe there is an explanation.
It's not a big deal, but not so straightforward to understand why something is not working for users, so may be worth addressing.
Apart from that, thanks a lot for grav, it's amazing :) :) :)
The text was updated successfully, but these errors were encountered: