Houston we have a problem. I’ve isolated a potential problem in upgrading to v2.0. For now I’d advise that you either a) don’t upgrade and wait for v2.1 or b) delete and re-install v2.0. The issue seems to be down to the way in which the plugin’s configuration options are saved between versions and I need some time to track this down and put in place a clean upgrade path.
Apologies in advance for this.
I’ve pulled the 2.0.0 release tag from the SVN repository but for now 2.0 is still showing as the current version; hopefully the next automatic sweep through SVN will pick this up.