Footnotify and a site redesign

Recently I found a really cool Chrome extension called Footnotify, which takes footnotes (as you see them on Daring Fireball or Wikipedia) and renders them as a hovering box when you click them. If you are a regular reader of either site (or, indeed, a plethora of others) you too might find it handy.

The extension’s elegance and ease of use made me want to put footnotes on my website, too, and so I started fiddling with various footnote extensions for WordPress. Eventually, I got a little disillusioned, since none of them were working quite how I wanted — as a result I sought out PHP Markdown Extra, which includes footnotes and also a host of other neat ways to write online. It’s based on the syntax developed by John Gruber, who runs Daring Fireball, and so the footnotes it generates are guaranteed to work with Footnotify, right?

Wrong. The WordPress theme I was using completely screwed footnotes up, and so I went hunting for a new one. I had been using The Unstandard, which is the theme I’ve successfully implemented and used over on the Leicester Sabres website. It’s a very good theme that’s very visually powerful — for the Sabres, that means that we draw people into the site and get them reading. However, I don’t really do my website for the hits, and so I’m unsure that the very visual theme was suitable. I ended up looking for a new, simple, one-column theme1 and eventually found Blaskan, which is now in use on the site.

As a result, I’ve installed a new plugin ([Markdown Extra]) and installed a new theme (Blaskan). However, they aren’t the only changes, since Blaskan also has good support for smartphones and as a result I no longer need the plugin that enabled the mobile view I previously employed. Good news all round!

There’s one small problem — for some reason, Footnotify doesn’t work properly on the individual blog entries. If you click a footnote on the main homepage it’ll work fine, but on the page for this post, it’s broken. I installed the JavaScript that enables it on a website, in case having it on the site rather than as a Chrome extension was helpful, but that hasn’t changed anything; I’ve gotten in touch with the author and hopefully this will eventually be resolved.

Edited to add: Initially, I had a problem with Footnotify. It would work fine on the homepage, but on the entries’ pages themselves, it didn’t work correctly. After sending a missive to Michel Fortin, I was able to identify it as an issue with a plugin on my website. Something was causing the relative footnote links generated by [Markdown Extra] to become absolute links, and thus breaking the Footnotify plugin. After some trial-and-error, it turns out that it was an issue with Joost de Valk’s Google Analytics for WordPress plugin. I visited de Valk’s website, where I read:

For plugin support, please use the appropriate support forums on WordPress.org. Plugin support emails will be immediately discarded. The only reason the option in the contact form below is there, is so I can more easily filter away those emails for those who don’t bother to read this text.

As such, I couldn’t be bothered to notify him of the bug in his plugin, and am instead using a plugin called Google Analytics which is much simpler to configure and works perfectly for what I need it to do. And now, footnotes work how they should — hurray!


  1. The eagle-eyed amongst you will have noticed that this theme is not one-column, since it has a sidebar. You’re entirely correct to notice that, but Blaskan can be configured to be one-column and so appears in several lists of such themes.