By Marc Barrot on Saturday, July 17, 2010 at 5:50 PM.
This should have originated within iJot.
Unfortunately it didn't. I had to type it from Scripting2, though I'm back in iJot now.
This is what I had typed in iJot
So this is a new post.
The first summit is typed in iJot, so is the rest of the outline.
My next step is to click the save icon in the toolbar, then check the 'save to scripting2 instead' option.
I should get the standard export to scripting2 dialog, with my scripting2 username, which I entered through the 'profile' tab of the 'Settings' page, pre-populated.
At that point I will enter my scripting2 password and hit 'save'.
I do not expect the outline to save to scripting2 just yet, as I placed a breakpoint.
But I will place an xml-rpc call to Scripting2.newPost, and will analyze the result response.
Ok, so the username was not pre-populated as expected (I can see why now), and the server wasn't either I expect.
After issuing my call to scripting2.newPost, I was returned an status 500 header, as well as an xml-rpc error message, errno 5, errstr: Didn't receive 200 OK from remote server.