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

[ecto Support]

I just joined this list. If there's any other list I should be on to  
prevent any future mishaps between ecto and WP let me know.

In response to

> A typical post publication scenario with the MT API is:
>
> metaWeblog.newPost
> mt.setPostCategories
> mt.publishPost
>

A typical post publish scenario with MT is actually:

metaWeblog.newPost
mt.setPostCategories
metaWeblog.editPost

That's always been the case with MovableType and TypePad. I  
personally confirmed that with Ben Trott back then when ecto was  
still Kung-Log. This was the case because mt.publishPost is slow on  
MT. See also:
http://www.jayallen.org/journey/2003/10/tip_xml-rpc_and_movable_type
I quote:

"After discovering my error, I slimmed the procedure down to one  
rebuild, like so:
Send a metaWeblog.newPost request with the publish boolean set to false
Set the category or categories using mt.setPostCategories
Set the publish boolean to publish using metaWeblog.editPost
I reduced the execution time of my script by about 75%. Whew..."

This is easily fixed in your WP:

When you get an metaWeblog.editPost without category info, first  
check if there are categories set already for that post id and use  
that, otherwise set the default category.

If you need a copy of ecto to test your xmlrpc changes, just let me  
know. ecto has a very useful console interface that allows you to see  
what is being sent and received over xmlrpc.

Adriaan