Opened 10 years ago
Closed 10 years ago
#31031 closed defect (bug) (invalid)
getRecentPosts returns an Exception
Reported by: |
|
Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | 4.2 |
Component: | XML-RPC | Keywords: | |
Focuses: | Cc: |
Description
I am trying to get recent posts using metaWeblog.getRecentPosts, It's returning the XML Exception:
Here is the stack Trace:
[XmlRpcIllFormedXmlException: Response from server does not contain valid XML.]
CookComputing.XmlRpc.XmlRpcSerializer.DeserializeResponse(Stream stm, Type svcType) +652
CookComputing.XmlRpc.XmlRpcClientProtocol.ReadResponse(XmlRpcRequest req, WebResponse webResp, Stream respStm, Type returnType) +190
CookComputing.XmlRpc.XmlRpcClientProtocol.Invoke(Object clientObj, MethodInfo mi, Object[] parameters) +1652
Change History (5)
#2
follow-up:
↓ 4
@
10 years ago
Additionally, I notice you've set the Version to 2.0.5, Are you actually running 2.0.5 and seeing the error there?
#3
in reply to:
↑ 1
@
10 years ago
Replying to dd32:
Would it be possible for you to attach an example of what the invalid XML is?
I'm suspecting a plugin notice or specific html content is triggering the issue, and it'll be hard to duplicate on a test install.
I did not get any XML. It just giving me the following message while dubugging.
"Data at the root level is invalid. Line 1, position 1."
#4
in reply to:
↑ 2
@
10 years ago
Replying to dd32:
Additionally, I notice you've set the Version to 2.0.5, Are you actually running 2.0.5 and seeing the error there?
The exact version of CookComputing.XmlRpc is v2.0.50727
#5
@
10 years ago
- Milestone Awaiting Review deleted
- Resolution set to invalid
- Status changed from new to closed
- Version changed from 2.0.5 to trunk
This sounds like there's a PHP Warning/Notice or other invalid data being output on your xml-rpc.php, you'll need to debug that further or test your client against a clean WordPress 4.1 install with no plugins and a default theme to rule out those causing the issue.
Unless you can show some invalid XML being created from WordPress, there's nothing we can fix in WordPress, so the Support Forums will be your best bet.
Would it be possible for you to attach an example of what the invalid XML is?
I'm suspecting a plugin notice or specific html content is triggering the issue, and it'll be hard to duplicate on a test install.