1.5.12 and ecto

I’ve tried the latest xmlrpc.php (the one posted by ryan above) and got an error saying “something wrong has happend” (according to ecto). How nice.

For me it’s okay you release an upgrade that often. It means you guys are working a lot, doing great, and WordPress IS great.
One thing that looks strange to me this time is one thing that metrixon said : you’ve “fixed” bugs in xmlrpc stuff and released it without testing even once. How’d you know you’ve fixed it if you’ve never tried it by yourself?
Basically I’ve no intention to complain nor blame, rather I come here and make posts to report bugs hoping that information helps you guys and other WP users, you know.

sorry wrong file. This is off my site:

https://phpfi.com/67760

Ecto 2.3.6 and the xmlrpc fix mentioned by Ryan above. Parsing error from Ecto and when I log into the browser I see that the post is sitting as draft.

Apologies for the topic being locked.
This second ‘page’ was inaccessible earlier due to other problems so any answers / posts to the first page would make no sense when the problem disappeared.

The xmlrpc fix will be announced as soon as possible.

I finally found an ecto user to help with debugging. We now have a fix. You need these versions of xmlrpc.php and functions-post.php.

functions-post.php
xmlrpc.php

Feedback appreciated. Finding testers has been a chore.

Hi ryan – sorry I could have helped out.
Anyway – just tried these two file replacements with ecto (v2.3.5) and had the following:

(1) Error when trying to upload image. Message was: Method “metaWeblog.newMediaObject” produced a server error: “Could not write file image.jpg

(2) I sent it as a draft and it didn’t arrive. No error just nothing. Opened ecto again and published it instead. This time it arrived as a draft! Work that one out!

(3) The category I had selected in ecto was lost by the time it arrived in wp and instead the default category had been selected instead.

I’ve been using ecto for a while flawlessly so these do appear to be new problems.Let me know if you want me to try anything else.

Ok. So I’m stupid!
Scrap the image upload problem. My own stupid fault. I had moved folders and it didn’t have the right permissions. Sincerest apologies for that one.
Still had the other two weird problems though. Am doing another test here.

Yep. Images are OK. I think perhaps I was hasty trying to look for the first one. I was slower going to look for the second one and by the time I opened up the Admin it had arrived.

Main problem left then is screwing up the selected category. It is ignoring the selected category on the client end and thus setting it to the default at the wp end.

Just want to confirm my experience is the same as YellowSwordfish (last posts). Something is different though — the process seems quite a bit slower now. But hey! it works, so thanks!

The category thing is a pain…

You’re right. It DOES seem slower which could explain why I got to my admin panel before the post arrived.
The category problem is a nuisance because if you care about categories it means you have to send everything up as a draft and then open the admin panel and edit the post. Which kind of defeats the object somewhat.
But hey – thanks for the fixes and for dealing with the main problem.It’s appreciated.

I am having similar problems with ecto that were not present before … When I publish a picture, I receive no errors, but once published, the picture is blank both in the post and when I click on it. the “uncategorized” by default is something that has been present since I began using ecto; I have accepted that as everything else with WP and ecto works for me.

Any advice on the picture issue? you can see it here – https://www.realcentralva.com

Try downloading Ryans fixes a few posts above. It has fixed the problem for a few of us. The category thing is still an issue.

I can also confirm that using Ryan’s two files from 6-30-05 above do indeed fix all the problems mentioned previously a€“ with the exception of the Default Category problem when using WP 1.5.1.3 and ecto 2.3.6.

Would it be too much trouble to bump version numbers when you introduce fixes? It makes it a lot easier to assess what needs to be done if the versions are coherent. 1.5.1.3 as it is now should be 1.5.1.4, in my book.

I’m not moving from 1.5.1.2 until this gets resolved for ecto users: we’ve already had to patch xmlrpc.php for that release to work properly.

Ryan just posted to the testers list:
“>Why there was no testing with ecto at all, baffles me.

Because I can’t install and test every XMLRPC client known to man,
because my requests for feedback from ecto users went largely ignored.
Very frustrating.”

Maybe some ecto users can offer to help next time – after all, someone should help.