-
-
Notifications
You must be signed in to change notification settings - Fork 7.6k
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
Support for lastmod in Org Mode timestamp formats #8536
Comments
This issue has been automatically marked as stale because it has not had recent activity. The resources of the Hugo team are limited, and so we are asking for your help. |
Sorry for the late response, yes, we should fix this. I suggest adding |
Thanks! My workaround is to use plain text ( |
PR gohugoio#7433 added support for Org timestamps for the DATE header. This PR widens the support with additional front matter headers LASTMOD, PUBLISHDATE and EXPIRYDATE. Fixes gohugoio#8536
@bep Created a PR for this. Would appreciate a review :) |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
I am using hugo v0.83.1+extended linux/amd64 BuildDate=unknown
Org Mode uses a timestamp format that is only partially
In issue 7433, Hugo was modified so that it could parse Org timestamps in the
.Date
variable.This does not seem to work when using the
lastmod
variable.Example:
#+lastmod: 2021-05-15
Renders as expected.
#+lastmod: <2021-05-15 Sat>
or#+lastmod: [2021-05-15 Sat]
does not render as the.Lastmod
parameter defaults to the.Date
variable.Would it be possible to have Hugo recognise Org Mode timestamps for all frontmatter date formats?
The text was updated successfully, but these errors were encountered: