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
# Writing
new_post_name: :title.md # File name of new posts
default_layout: post
titlecase: false # Transform title into titlecase
external_link: true # Open external links in new tab
filename_case: 0
render_drafts: false
post_asset_folder: false
relative_link: false
future: false
Your theme _config.yml (Optional):
N/A
Hexo and Plugin version(npm ls --depth 0):
hexo@3.3.9
For BUG
BUG description:
If hexo is set not to show future posts, then if the server is started before the post become visible, the post will not be shown even if the timestamp had past.
When doing hexo g after the timestamp had past, the post can be generated properly in public folder.
The way to reproduce
Configure hexo not to show post in future.
Start the hexo server.
Create a post that will become visible in future.
Refresh the page without restarting the server after the timestamp goes into past, the post will still not be visible.
I believe this is what hexo intend to do so (because the future is set to false). As it is a static website generator, there is no dynamic loading in hexo process. Every post has to explicitly run the hexo g to be generated.
Although the hexo s listens all files changing, it only is triggered when the change event emitted. Moreover, the hexo s is designed for the testing purpose.
Even though hexo server could periodically check the post date, other static website hosts couldn't do the same, like Github.
Environment Info
Node version(
node -v
):v6.11.3
Your site
_config.yml
(Optional):Related config:
Your theme
_config.yml
(Optional):N/A
Hexo and Plugin version(
npm ls --depth 0
):hexo@3.3.9
For BUG
If hexo is set not to show future posts, then if the server is started before the post become visible, the post will not be shown even if the timestamp had past.
When doing
hexo g
after the timestamp had past, the post can be generated properly inpublic
folder.N/A
Related
#188
The text was updated successfully, but these errors were encountered: