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
I noticed a bug recently in the Blog plugin: I don't exactly know when or why it happened, but as of recently, footnotes are no longer properly parsed. I did not change the syntax and double-checked for eventual syntax errors, but it appears the Markdown parser doesn't like footnotes anymore. This behavior is visible both when outputting post.content_html | raw on the page as well as in the preview field in the backend.
Interestingly, this did work in the past. And even more so, since the blog plugin "caches" the rendered HTML in the content_html variable, the old posts with footnotes still work. To give you an example:
A recent post I published a few days ago. You can search for [^1] to discover that the markup is not rendered. This post lets me assume this bug has been there at least since July.
Heya!
I noticed a bug recently in the Blog plugin: I don't exactly know when or why it happened, but as of recently, footnotes are no longer properly parsed. I did not change the syntax and double-checked for eventual syntax errors, but it appears the Markdown parser doesn't like footnotes anymore. This behavior is visible both when outputting
post.content_html | raw
on the page as well as in the preview field in the backend.Interestingly, this did work in the past. And even more so, since the blog plugin "caches" the rendered HTML in the
content_html
variable, the old posts with footnotes still work. To give you an example:[^1]
to discover that the markup is not rendered. This post lets me assume this bug has been there at least since July.Current versions:
v1.2.3
v2.0.2
The text was updated successfully, but these errors were encountered: