I have been working on WordPress XMLRPC in depth connected to the Kish Multi Pro Plugin for more than a year now. For some WordPress users who are using my plugin they get the “not well formed” error which made to go for debugging the response what we receive from that particular WordPress blog.
There is an issue with the XML response and could not be parsed which triggered this error.
What could be the reasons?
- I had a deep look on the posts that are triggering this error. There could be some letters which are creating the XML validation error
- Two of such issue was sorted out by re-installing the WordPress.
- One was sorted out by deactivating a plugin which was creating this problem.
- Could be that the XMLRPC.php file is having some issue.
Why is Kish Multi Pro getting this error
Its nothing related to the plugin. This plugin will display the information, only if it gets the right information and is served by the configured WordPress site. To sort out this issue, we need to correct the problems in the configured WordPress site.
Related posts:
- Error After WordPress 3.0 Upgrade One of my plugin on one of my blog is...
- Updating post custom fields using XMLRPC – WordPress Updating the custom data of a post which can be...
- Do you blog from your feed reader? Do you start writing your blogs posts inspired by reading...
- Compatibility of Plugins : KishPress Plugins works well with WordPress 3.0 I upgraded all my blogs to WordPress 3.0. I have...
- WordPress Comment Moderation Tool (WordPress Plugin) There are many blog owners who get tons of comments...
You should have got the notification to upgrade your WordPress Installation. Most of us do it instan → 
There are many blogging softwares like Joomla, WordPress, Drupal, etc, but I would suggest you to go → 
I always wait for beta releases and love to test it and try to know about the new features, and also →
{ 8 comments… read them below or add one }
As far as I know UTF8 characters can’t go trough XMLRPC. I’m trying to find a solution myself for my app.
Solution found : utf8_encodePass trough XMLRPC fine then
Hi can you let me know the solution in details. I may need it as I work on XMLPRC projects
“There could be some letters which are creating the XML validation error”This helped. I cut some content off another website, there was a Unicode character in there preventing me from posting through ScribeFire.
Hey, did you find a solution? I am facing the same problem. Please let me know. Thanks.
There could be many reasons, needs to be debugged to find the exact problem
Are you escaping your xml characters ? See http://stackoverflow.com/questions/1091945/where-can-i-get-a-list-of-the-xml-document-escape-characters
Wow, friendly froggy gets my award for the day. His is the only reference that worked and solved my parse error. It was a simple change. I simply added this line under the existing variable: $ireviews = utf8_encode($ireviews);That did it. Error went away. Sending kudos out for this post!!! –Richard
{ 1 trackback }