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
a041f09 improved the display of .LastMod so that it's only displayed when different from .Date.
However, when using .GitInfo to automatically populate .LastMod from the date of the last commit touching the file in question, this logic pretty much never fires and .LastMod is always displayed.
What's really needed is to display .LastMod only if the formatted.LastMod is different from the formatted.Date.
If that's difficult, it would help to change the nehere to a lt so that I can manually set the article date to a date after the commit that published the article and prevent the display of .LastMod this way.
Theme version
v2.3.1
Hugo version
v0.101.0
What browsers are you seeing the problem on?
Firefox, Chrome, Safari, Microsoft Edge
Relevant Hugo log output
No response
The text was updated successfully, but these errors were encountered:
Thanks for the report, @mika-fischer. I'll make a change so that both dates are formatted prior to checking their values. Hopefully this will address the issue you're seeing.
What happened?
a041f09 improved the display of
.LastMod
so that it's only displayed when different from.Date
.However, when using
.GitInfo
to automatically populate.LastMod
from the date of the last commit touching the file in question, this logic pretty much never fires and.LastMod
is always displayed.What's really needed is to display
.LastMod
only if the formatted.LastMod
is different from the formatted.Date
.If that's difficult, it would help to change the
ne
here to alt
so that I can manually set the article date to a date after the commit that published the article and prevent the display of .LastMod this way.Theme version
v2.3.1
Hugo version
v0.101.0
What browsers are you seeing the problem on?
Firefox, Chrome, Safari, Microsoft Edge
Relevant Hugo log output
No response
The text was updated successfully, but these errors were encountered: