[@briantoronto Participant 13 years ago]

Had the same issue. I rolled back the plug-in to 2.0.3 and it fixed the issue for me.

Brian