Closed fusion809 closed 4 years ago
Do you have a link so I can check the html code produced?
@celsomiranda I update this plugin and then footnotes in the already existed pages fail, while it works well in the new created pages even its contents is totally same as the existed one. How strange!!
I think it owns to the hexo but not this plugin. Maybe hexo will not change the output for the md file which have not been changed, even if we clean up the output folder.
maybe something changed upstream, i honestly don't know. :( I don't even have the time to experiment with hexo anymore :(
i have the same problem
I had the same problem. But I resolved it because I use hexo clean
and then retry hexo g
.
As @Edenharder said, maybe hexo is bad. You should clean a build cache.
I update this plugin and then footnotes in the already existed pages fail, while it works well in the new created pages even its contents is totally same as the existed one.
Hexo heavily cache the content, run hexo clean
to clean the cache as previous comment suggested.
Hi,
I have added this:
to my
_config.yml
(i.e., the one in the top-level directory of my hexo-site). I also added:to the
dependencies:
section of mypackage.json
file. Then I rannpm install && npm uninstall hexo-renderer-marked
. I then started my Hexo server and my footnotes are being left un-rendered. That is, my in-text footnote is:[^1]
and at the end of my post I have the footnote:
[^1]: Which in itself is a variant, or distribution of Linux.
they are left as is in the post.
Thanks for your time, Brenton