Okay, so, uh, not quite sure how to explain this but it looks like something stole a line of code... We've got it back though and reinstated it so the next update should have this fixed. Sorry about that!