Thread Starter
Hamrin
(@hamrin)
Hi,
My problem was that I managed to get a URL-encoded “&” (%26) into the service url. Try looking into that, but also notice that there’s been an update to the plugin (2.0.2) and the changelog mentions a fix in update 2.0.1. My error was supposedly local and in v2.0.0.
Thread Starter
Hamrin
(@hamrin)
Thanks to excellent help from the author this now works like a charm. I managed to sneak a url-encoded & into the service url which messed things up…
Thread Starter
Hamrin
(@hamrin)
I’ll elaborate some more on my issue; the problem I have is that I keep getting “INVALID API CALL” when trying to test the ‘test’ service (in a browser). Apparently this will happen when the service is not found, but I cannot see what I could have missed, as I have followed the instructions.
