Wordpress XMLRPC - 32700 parse error - Mystery Solved
If you are using XMLRPC to post to Wordpress(WP) Blogs and are struck to an error 32700 parse error. not well formed here is a good news to you...
This was causing me trouble for few months,Hours of searching on google did not do anything
Some people claimed its due to some code manipulation in xmlrpc.php but that was not true
The real cause of problem is the admin password you are using,since last few version WP is giving password very randomly with characters like & @ # ( )
These password don't work with XMLRPC.I think specially & is the biggest problem.so the solution is simple reset your WP password to remove these characters and you are all set to go...
If you need any assistant feel free to email me at
Hope this helps other people,post a comment below if this was
This was causing me trouble for few months,Hours of searching on google did not do anything
Some people claimed its due to some code manipulation in xmlrpc.php but that was not true
The real cause of problem is the admin password you are using,since last few version WP is giving password very randomly with characters like & @ # ( )
These password don't work with XMLRPC.I think specially & is the biggest problem.so the solution is simple reset your WP password to remove these characters and you are all set to go...
If you need any assistant feel free to email me at
Hope this helps other people,post a comment below if this was
posted by Komal @ 1:26 AM
1 Comments:
At March 7, 2010 at 11:22 PM ,
Amit Shah said...
Well that may be 1 of the issue that you may have suggested, but i too encountered the same with the error and no special characters in the user / password. Still i got errors. What i discovered that what it dose is it reads only 4096 chars at a time and at times your content is bigger than that. And it, instead of joining it together and proceeding, it adds \n at the end on the line that looks like this
$contents .= trim($line) . "\n";
This additional \n in the content is what use to kill for me. I removed it and now the issue is resolved and working smooth.
On further debugging what i discovered that what use to happen is that it use to break up the content at some place in such a manner that it couldn't be parsed when the rest moved on the next line like
....&qu
ote<message.....
now in such case the parser is obvious to have error in this case. Removing the "\n" from the code solves it. Enjoy.
Post a Comment
Subscribe to Post Comments [Atom]
<< Home