[wp-xmlrpc] Loosing text in more tag

[Joseph Scott]

On May 1, 2008, at 3:12 PM, Peter Westwood wrote:

> Hmm. Back in the day this worked for xmlrpc.
>
> I remember writing the patch that made it work!
>
> The original ticket was [1] - what was the reasoning behind the  
> changes
> in 2.5 that removed this feature from xmlrpc posts - was it to better
> implement the API as per standards?
>
> [1] http://trac.wordpress.org/ticket/2991


If I'm reading the diffs on that ticket right, the assumption was  
that the <!--more--> tag would be in-lined as part of the  
"description" field (in XML-RPC) and not make use of the  
"mt_text_more" field.  I haven't tried it, but I suspect that would  
probably work.  That would make it possible to create a new post via  
XML-RPC that uses a custom more text, although it should be noted  
that this should be done via the mt_text_more field.  Unfortunately  
it would still run into the case that outlined before:

1 - User creates new post in wp-admin which includes <!--more My  
Custom String Here -->
2 - User fetches the post via XML-RPC
3 - XML-RPC in WordPress has no knowledge of the 'My Custom String  
Here' part, so that essentially is lost

You don't even have to create the post in wp-admin for this to be  
true.  And the reason for that is WordPress will break the post into  
the description and mt_text_more fields for metaWeblog.getPost, the  
raw <!--more--> is never included and is therefore lost.  At this  
point the blog client has no way of knowing that what was really used  
was <!--more Some Custom Text Here-->.

At this point I still think that a new field is going to be needed to  
store the breaking tag text in order for this to work.

--
Joseph Scott
joseph at randomnetworks.com
http://joseph.randomnetworks.com/