We’ve found the culprit and are in the process of fixing it. 
(It was an errant <noscript> tag from a post that we pulled in through RSS and it upset some things… 
).
4 Likes
We’ve found the culprit and are in the process of fixing it.
(It was an errant <noscript> tag from a post that we pulled in through RSS and it upset some things… ).