Hey Mojowill. We’re working on our 2.1 release now; we feel your pain on this and apologize if the plugin gets worse with each release. While we’re trying to patch everything we can from release to release, some things inevitably get broken and others not fixed for everyone – things we don’t realize until it’s out there being used by folks on a bunch of different setups. If you’re interested in testing out new code as it becomes available – but not necessarily officially released – you can always feel free to email me (rob at tri.be) and I can get you what we’ve currently got at that moment in time. This way if we do fix it along the way you aren’t waiting for an official release to get something that we’ve already fixed. We do want to make this right by you guys, though, and apologize for persistent problems like this.
Josh: awesome to hear the PRO route fixed your issue. We’re working hard to get this resolved for core/free users, too, so they don’t feel like upgrading to PRO is necessary for a working plugin.