-
-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[BUG] page.post template variable behaves differently when using hexo serve
and hexo generate
#2451
Labels
bug
Something isn't working
Comments
hexo serve
and hexo generate
hexo serve
and hexo generate
looks like this is related also to: #2454 |
I'm not sure if I'm clearly understand the issue. Is that possible to have some screenshots? |
@NoahDragon Still using the Repo I created earlier, see this: Note that the rendered page title ( |
Let me have a look. |
This was referenced Apr 9, 2017
2 tasks
It's caused by fragment cache. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
BUG Description
I'm using
page.post
variable when rendering pages to support multi-language.When using
hexo serve
command, the variable works as expected and gives the page's absolute path.However when using
hexo generate
command (orhexo deploy
), when rendering blog posts, thepage.post
variable givesindex.html
, which is unexpected.Bug Detail
I've create a repo to isolate and test this bug. I make the page.post variable display as header of the post, and it seems that when using
hexo generate
, thepost.path
andpath
stays the same between pages. When I create atest/hi.md
static page, all other pages has path=test/hi.html
.Way to reproduce bug
See above.
Environment Info
Node version(
node -v
)Hexo version
Your site
_config.yml
(I use a self-modified version of theme chanYour theme
_config.yml
Plugin version(
npm ls --depth 0
)I've customized hexo-generator-category to change the path it generates.
The text was updated successfully, but these errors were encountered: