hexojs / hexo-renderer-markdown-it

Markdown-it is a Markdown parser, done right. A faster and CommonMark compliant alternative for Hexo.
MIT License
349 stars 60 forks source link

Footnotes failing, even after plugin configuration set in _config.yml #37

Closed fusion809 closed 4 years ago

fusion809 commented 8 years ago

Hi,

I have added this:

markdown:
  plugins:
    - markdown-it-abbr
    - markdown-it-footnote
    - markdown-it-ins
    - markdown-it-sub
    - markdown-it-sup

to my _config.yml (i.e., the one in the top-level directory of my hexo-site). I also added:

    "hexo-renderer-markdown-it": "^3.4.1",

to the dependencies: section of my package.json file. Then I ran npm 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

celsomiranda commented 8 years ago

Do you have a link so I can check the html code produced?

Edenharder commented 8 years ago

@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.

celsomiranda commented 8 years ago

maybe something changed upstream, i honestly don't know. :( I don't even have the time to experiment with hexo anymore :(

jasonzhouu commented 6 years ago

i have the same problem

OldBigBuddha commented 4 years ago

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.

curbengh commented 4 years ago

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.