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
As discussed in #6998 (reply in thread), the post date by default contains a time was well, which is set to 12:00AM. It should display only a date, regardless of whether the page header contains only a date or a date and time. This has also been observed in #6996.
While is is possible to fix this through customization, the default should be only the date.
Note that the default was date only as late as 9.5.13+insiders.4.53.1.
Thanks for reporting. This is a regression of accepting and merging #6981, which switched to format_datetime instead of format_date. The predefined format long will now refer to a format string that includes the time. Rendering the blog post without time should be the default, as our current assumption is that that's what most users would expect.
1041766 adds a condition that checks if the author uses one of the predefined time formats, the blog plugin should use format_date. However, if a custom string is given, the plugin will make use of format_datetime, so we allow explicitly opting into using format strings including time. This still fixes #6981 but allows us to keep sensible defaults.
Context
Use of the blog plugin without further settings.
Bug description
As discussed in #6998 (reply in thread), the post date by default contains a time was well, which is set to 12:00AM. It should display only a date, regardless of whether the page header contains only a date or a date and time. This has also been observed in #6996.
While is is possible to fix this through customization, the default should be only the date.
Note that the default was date only as late as 9.5.13+insiders.4.53.1.
Related links
Reproduction
9.5.16+insiders.4.53.4-datetime-blog.zip
Steps to reproduce
Browser
No response
Before submitting
The text was updated successfully, but these errors were encountered: