[wp-testers] [Fwd: 1.5.1.3 and categories]

[Aaron Brazell]

Coming to Ryan's defense on this one... Ecto is not "our" (used loosely)
product. "Our" product is WordPress. The fact that you can use Ecto should
be seen as a bonus, not a requirement. Same with any other non-WP tool.

--
Aaron Brazell
Editor, Technosailor.com
"So Long, and thanks for all the fish"
  -Hitchhiker's Guide to the Galaxy
 
-----Original Message-----
From: wp-testers-bounces at lists.automattic.com
[mailto:wp-testers-bounces at lists.automattic.com] On Behalf Of Ryan Boren
Sent: Saturday, July 02, 2005 12:55 PM
To: wp-testers at lists.automattic.com
Subject: Re: [wp-testers] [Fwd: 1.5.1.3 and categories]

On Sat, 2005-07-02 at 08:11 -0700, Matthew Mullenweg wrote:
> 
> -------- Original Message --------
> Subject: 1.5.1.3 and categories
> Date: Sat, 2 Jul 2005 22:17:33 +0900
> From: Adriaan Tijsseling <adriaan at neoteny.com>
> To: Matthew Mullenweg <m at mullenweg.com>
> 
> Matt,
> 
> The latest 1.5.1.3 (there were several code changes in the same
> version, I'm referring to the latest one) totally messes up category
> support in xmlrpc. Whoever coded that does not realize that with the
> MovableType API, the categories are set via mt.setPostCategories, not
> via editPost or newPost. What happens is that after
> mt.setPostCategories, the call to editPost removes any categories set
> in mt.setPostCategories.

A typical post publication scenario with the MT API is:

metaWeblog.newPost
mt.setPostCategories
mt.publishPost

Works fine for me on all clients I possess.

> 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.

Ryan

_______________________________________________
wp-testers mailing list
wp-testers at lists.automattic.com
http://lists.automattic.com/mailman/listinfo/wp-testers