MT 3.2 issue - External tools using XML-RPC don't work.

I use ZEMPT (0.3) as a frequent posting tool. I also use MEOW, a simple email-to-post convertor. Both of these tools rely on the XML-RPC interface to get their content into MT. Both have stopped working.

I read in a post from another user that technical support suggested that "mt-xmlrpc.cgi" from the previous version could be tried. I tried the version from MT v2.661. The same problem.

I understand from other writers that other external programs are not able to post via the XML-RPC interface any longer.

Given all this I'm assuming this *is* a bug. It would be good to know that this issue is logged and being worked on.

Thanks, Josiah

Sounds like the same problem as this thread:

http://www.movabletype.org/support/index.p...=ST&f=8&t=54041

Make sure you report it to Six Apart (open a support case). It seems to be a growing issue but they have not yet commented on it that I know of.

I was in cuckoo land.

I mis-typed API password into ZEMPT and put it in the wrong slot in MEOW. ouch... both now work fine.

I would love the facility to delete posts ...

Where do you put the API password at?

1 - you define it in MT for each author using a posting tool at:



the API Password slot is near the bottom of the page.

2 - use this new password in your blogging tool to enable it to post

regards, josiah

must be a different issue, because I'd already changed that password to something I could remember and still getting error 144.

tboucher, you're getting this problem, which is NOT the same as the API password issue:

http://www.movabletype.org/support/index.p...=ST&f=8&t=54041

That's an MT bug and I suggest you open a support ticket:

https://secure.sixapart.com/t/help?__mode=edit

So far, Six Apart are ignoring the problem completely (or at least staying mum about it), but eventually, if enough of us report it, I'm hoping they'll get it resolved. This bug makes external editors useless, and needs to get addressed.

I'm getting the same problem with ecto. (My API password is correct.)

What brought me to this thread, though, is that I can't post pix from Flickr to my new MT 3.2 installation (brand new: never used MT before). I have a hunch that this "144" error is getting spit back to Flickr when I try to do a test (or actual) post. Flickr interprets this as an incorrect username/pw, even though Flickr uses that same username and password was successully retrieve the list of blogs from my site.

Given this thread, and the problem karlelvis is having in another one, I'm definitely getting the sense that xmlrpc is screwed up a bit under MT 3.2

Any ideas, SA?

I got a patched version of XMLRPCServer.pm from SA last night that I'm testing, with what looks like good results. I don't know when they plan to release it, I'm trying to find that out now.

I got the same problem with about the same configuration.

I'm really longing for a patch.

I talked to Six Apart's Manager of Technical Services, who confirmed that this fix hasn't be 'officially released' - she said licensed users who need it must contact SixApart support - https://secure.sixapart.com/t/help?__mode=edit (requires a typeKey login w/valid account)

They don't yet have a solution for 'those with unsupported licenses', but they said they hope to be able to post something in here or the Knowledge Base soon (which sounded like 'next week' to me).

A kind soul has posted a link to the amended file.

You know, I'm gettin' a little irritated that six apart are still not addressing this. Users need the fix and it's such a simple fix...