Ah, thank you for bringing this to my attention!! I've went in and updated the code that was causing the error. This fix (plus some other fun stuff!) should be live shortly!
