I've been noticing that the WordPress iPhone app, and others that use xmlrpc, publish munged posts on my blog. The < characters in code (images, links, paragraphs...) are stripped out, leaving invalid and ugly hacked markup.
Any ideas?
I've been noticing that the WordPress iPhone app, and others that use xmlrpc, publish munged posts on my blog. The < characters in code (images, links, paragraphs...) are stripped out, leaving invalid and ugly hacked markup.
Any ideas?
You might try the normal remove plugins, etc. to narrow down the problem.
I am using xmlrpc to publish from word with no problem including graphics, etc. so I would think a plugin problem.
This is caused by a change in libxml2, which is used by PHP to parse the XML portion of XML-RPC. Long story short, upgrade to PHP 5.2.9 and libxml2 2.7.3 and it will work again. You must upgrade both, not just one, in order for things to be fixed. For the longer story you can read my posts on the subject:
http://josephscott.org/archives/2008/12/problems-with-libxml2-for-wordpress-xml-rpc-users/
http://josephscott.org/archives/2009/02/update-on-libxml2-issues/
http://josephscott.org/archives/2009/03/conclusion-of-libxml2-issues-use-php-529-libxml2-273/
I just set up a fresh copy of WordPress 2.7.1, with nothing additional installed - just a barebones install of WordPress as distributed through wordpress.org
It's showing the munged xmlrpc-published posts, too.
Could there be something funky on the server? I'd assumed the xmlrpc code was pretty much self contained, so wasn't thinking it could be a server thing.
If ypu want to send me the user name and password for your test install I will send a post from Word.
It's a problem with the server setup, not WordPress. The PHP configuration is using a version of libxml2 that is stripping the brackets ( < ) from the XML-RPC requests.
I won't be able to update either PHP or libxml2 on the shared server, but applied the suggested code from http://blog.hoofoo.net/2009/01/14/wordpress-patch-for-problamatic-libxml2-version/ and it appears to work now.
You should contact your hosting service then and let them know they are running versions of PHP/libxml2 that are known to be broken.
You must log in to post.