Use "publishdate" as default for "date" ?

[jcw]

A small feature request, if I may...

I write all my posts in advance, and then publish them on specific days at midnight (I've been doing this for years, switched from WP to Hugo a few months ago, and am so glad I finally did! - FWIW). I'm about to streamline the process by having Hugo regenerate and upload the weblog daily at midnight.

This can be automated by entering a publishdate = "...", which is great. But I still need to enter the date = "..." field as well.

Would it be possible to auto-set the date field from the publishdate, if none is present?
Or to put it differently: make the date field default to publishdate?
Right now, omitting the date value will timestamp the posts as Jan, 0001.

Assuming I'm not overlooking some feature in Hugo.
It's a small change, I hope - but just that little nudge extra to make posting more enjoyable still...

Cheers,
-jcw

PS. And a minor minor bug report, I think: the "9 of 0" below should perhaps be "9 of 9"?

Change detected, rebuilding site
2016-05-13 21:04 +0200
0 draft content
9 of 0 future rendered
132 pages created
[...]

[bep]

Yes that makes sense.

[g3wanghc]

@bep Future rendered bug fix on 836e3a7

[mubix]

Agreed, I'd love not to have the exact same data in my posts twice (more chance for me to mess them up)

Originally when I started looking into "Future content" I couldn't find any documentation at all on how to set them up. (Google for "Hugo Future Content" or "Scheduled Posts" didn't result in much). So I just tried to set the date in the future. No joy. However I think that would be the intuitive move here. Just check date to see if it's in the future instead of separate fields. Unless there is a valid reason for keeping them separate.

[kaushalmodi]

+1 for this feature.

In addition to what the OP said, if both data and publishdate are set in the frontmatter, then please set .Date to return the publishdate.

[kaushalmodi]

I have found this workaround for now: https://discuss.gohugo.io/t/how-to-use-the-publishdate-if-both-publishdate-and-date-are-set-in-frontmatter/5142/2?u=kaushalmodi

[graemebenzie]

Line 31 https://github.com/netlify/netlify-cms/blob/caa5c69522e5446e8677775d7ea25fdbb0e2b36e/src/backends/backend.js

I found that I got this error because I had removed the Title field for the collection. For anybody stuck out there and googling

[stale]

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.
If this is a bug and you can still reproduce this error on the master branch, please reply with all of the information you have about it in order to keep the issue open.
If this is a feature request, and you feel that it is still relevant and valuable, please tell us why.
This issue will automatically be closed in the near future if no further activity occurs. Thank you for all your contributions.

[vassudanagunta]

This is the current code:

	if p.Date.IsZero() {
		p.Date = p.PublishDate
	}

	if p.PublishDate.IsZero() {
		p.PublishDate = p.Date
	}

@bep Shouldn't this be marked as fixed?

[kaushalmodi]

@bep @vassudanagunta

I think the issue is that the date in .Page.Params is left unset if only publishdate is set.

Test case

• Markdown | Hugo output

Notice the Page Params (Debug) section in the Hugo output linked above. Just as lastmod is auto-set based on publishdate, the request is that date also be auto-set if publishdate is specified, but date is not specified explicitly in the front-matter.

[vassudanagunta]

@kaushalmodi

Since this issue is nearly 2 years old, and was fixed by #3854 per its title and description quite a while ago, I'd say create a new issue for what you describe.

[kaushalmodi]

@vassudanagunta I can create a new issue, but the test case I linked simply shows that the request in the original post of this issue is not met:

Would it be possible to auto-set the date field from the publishdate, if none is present?

[github-actions]

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.