Footnote link back to article text: <a href=”#ref1″>↩</a></code>
But what you currently have is <a href=”#fn-E9Mru3HsHeKH8GsTZ-1“><sup>[1]</sup></a> for the in-page link and <a href=”#fnref-E9Mru3HsHeKH8GsTZ-1”>↩︎</a> for the footnote link back to the text. There’s no id=”fn-E9Mru3HsHeKH8GsTZ-1“ nor id=”fnref-E9Mru3HsHeKH8GsTZ-1” in the html to indicate where these links should go.
A quick fix might be to just enter in the appropriate id attributes in the anchor links to footnotes and in the p tag for each footnote, but I suspect that the long alphanumeric part here means that you’re using some program that has messed this up, so it may be a better use of time to figure out what went wrong with the program.
EDIT: After searching how to properly format code in comments on the EA Forum, I happened to come across this advice to just use this Google Docs add-on to make including footnotes much easier. It’s likely more worthwhile for you to ignore the advice I made above and instead just use the add-on. (I still don’t know how to make text appear in code blocks, though.)
The post in question was not made using markdown, but rather our built-in WYSIWYG editor. That editor does not do footnotes currently. I’m guessing the footnotes were pasted in from Google docs, which would explain the broken internal links.
The issue is that the html is missing both the id attributes that show where the links should take you. What you want is something like:
In-page anchor links: <a id=”ref1“ href=”#fn1”>¹</a>
Linked footnote: <p id=”fn1″>¹ <small>Footnote text.</small></p></code>
Footnote link back to article text: <a href=”#ref1″>↩</a></code>
But what you currently have is <a href=”#fn-E9Mru3HsHeKH8GsTZ-1“><sup>[1]</sup></a> for the in-page link and <a href=”#fnref-E9Mru3HsHeKH8GsTZ-1”>↩︎</a> for the footnote link back to the text. There’s no id=”fn-E9Mru3HsHeKH8GsTZ-1“ nor id=”fnref-E9Mru3HsHeKH8GsTZ-1” in the html to indicate where these links should go.
A quick fix might be to just enter in the appropriate id attributes in the anchor links to footnotes and in the p tag for each footnote, but I suspect that the long alphanumeric part here means that you’re using some program that has messed this up, so it may be a better use of time to figure out what went wrong with the program.
EDIT: After searching how to properly format code in comments on the EA Forum, I happened to come across this advice to just use this Google Docs add-on to make including footnotes much easier. It’s likely more worthwhile for you to ignore the advice I made above and instead just use the add-on. (I still don’t know how to make text appear in code blocks, though.)
EDIT Jan 2022: The EA Forum now supports rich footnotes. Use that instead!
The post in question was not made using markdown, but rather our built-in WYSIWYG editor. That editor does not do footnotes currently. I’m guessing the footnotes were pasted in from Google docs, which would explain the broken internal links.