Maybe there is something I’ve missed.
It’s not a major problem. I’ll let you know if I find a solution.
Yep that works fine. I pretty much installed the plugin in a vanilla WordPress set up. Just so I could test it.
Have I missed a dependency or something?
It’s Chrome on a Mac OS X.
It’s possible it could be a local server set up issue. However I’d appreciate it if you took a look.
I’ve seen this error occur before on similar applications and the solution has been to use jsonp or edit the headers.
