Thread Starter
Dave5
(@dave5)
Fixed it by rolling the plugin back to it’s previous version using WP rollback 🙂
Thread Starter
Dave5
(@dave5)
Also I’ve just upgraded to 1.5 and it seems like the problem happened since then – not sure if relevant or not. I’ve read that it happened with earlier version but 1.4 fixed it.
