Forums
(@ardnoosh)
13 years, 8 months ago
This is a WordPress bug.
Upgrading to 3.4.1 (and subsequently 3.4.2) from 3.3.1 caused this.
Downgrading the version fixed everything.
Something for WordPress dev to think about.