I’m test-driving micro.blog to see how I feel about it (the mix of short and long-form posting, together with cross-post, seems great), but it doesn’t seem to have imported footnotes correctly from my WordPress blog, as in, none of them shows up.
To be fair, I don’t have that many posts using footnotes, but the post editor is full of WP-specific codes (I imagine they aren’t filtered out on import), making it a bit hard to find the footnoted parts and re-add them manually. Is there any workaround for this, or I’ll have to edit post by post?
I should say that, other than this, it’s one of the best WP-imported results I’ve seen, with apparently no other issue, which is awesome.
I suspect you’re using a Wordpress plug in of some kind with special syntax? There probably can be an improvement to the importer, but I have another idea-- make a category for “hasfootnotes” and then go to “edit filters” from your category page. Add a filter for the syntax you used on Wordpress and apply it to all existing posts that match. Then you could click on that category to get just those posts and edit them to use the standard Markdown footnote syntax.
I’m actually not using any plugins on WordPress, except some for syndication and the IndieWeb. But all of my posts are written in Gutenberg, and I suspect the “WP-specific code” I see in the source is from their block-based interface.
Now, I activated “code view” on WordPress to check something and noticed it doesn’t show the footnotes there too, so in the end it must be a WordPress export issue and not a micro.blog import one, as the footnotes seem to be literally missing from the exported code. I guess I’ll have to re-add them manually until I find a fix for the export.
Thanks for your answer, it gave me the idea to check the WP post in code from inside WP.
Good to know, thanks y’all. This does sound like a WordPress issue. If you want to send me your WordPress export (to help@micro.blog) and tell me which post has a footnote, I can see if there’s a work-around on our side. Also maybe some kind of WordPress find-and-replace plugin could convert the footnote to a Markdown footnote, just a random idea.
I was checking the xml here (I’m not a developer, but I understand a bit of code) and found the footnotes entrenched somewhere along it, so it seems WordPress does export them, it’s just… in a weird place, linked in a weird way.
I’ll send you the xml via email. Meanwhile, I might try the Markdown upload (I found a WP plugin that exports for Jekyll and it keeps the footnotes intact).
Markdown seems to be working perfectly! There’s some weird stuff going on with some syntax, but this time I can clearly see that something went wrong with the WP export.
And again, regarding the WP import, other than the missing footnotes, everything else was perfect, which is miles ahead of other platforms I tested that would import stuff from WP. I just want to congratulate you on that.