JavierCane

Hi,

I’ve had the same problem described by fatwombat and I could solve it as it says (deactivating and reactivating the plugin, thanks a lot for that comment!)

shawn: firstly I have to congrats you for the good work with the plugin, but I also think that you should releaase a hotfix for this situation since may be a lot of people are upgrading the plugin without noticing this error and finding this post.

Thanks a lot for your work guys!