[wp-trac] [WordPress Trac] #8013: CDATA block in post content trips up XMLRPC interface

[WordPress Trac]

#8013: CDATA block in post content trips up XMLRPC interface
------------------------+---------------------------------------------------
 Reporter:  redsweater  |       Owner:  josephscott
     Type:  defect      |      Status:  new        
 Priority:  normal      |   Milestone:  2.8        
Component:  XML-RPC     |     Version:  2.6.1      
 Severity:  normal      |    Keywords:             
------------------------+---------------------------------------------------
 This issue was originally discussed on my forums:

 http://www.red-sweater.com/forums/viewtopic.php?id=948

 Summary: If a post contains a CDATA block it causes a "not well formed"
 parse error in WordPress.

 I narrowed the issue down to a very simple test case, typing the following
 into the content of a blog post from MarsEdit causes a parse error in
 WordPress:

 <![CDATA[Hello]]>

 I confirmed that the same content also triggers the error if sent from
 another Mac desktop client, ecto.

 By the time MarsEdit massages the content, it's literally:

 &lt;![CDATA[Hello]]>

 So, to reproduce the bug either paste the unmodified line into MarsEdit or
 else use an XMLRPC testing tool to send a post with the literal content as
 escaped above.

 As far as I can tell this should be legal XML content, but it trips up
 WordPress. I also notice that it trips up Movable Type, but since I had
 started a conversation with Joseph Scott about this, I'll use this as the
 exploration vector for the bug.

-- 
Ticket URL: <http://trac.wordpress.org/ticket/8013>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software