Summary: | KBlog generates invalid structured XML-RPC requests for the metaWeblog API | ||
---|---|---|---|
Product: | [Applications] kdepimlibs | Reporter: | Berend Dekens <kde> |
Component: | kblog | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | normal | CC: | christian_weilbach |
Priority: | NOR | ||
Version: | 4.2 | ||
Target Milestone: | --- | ||
Platform: | Gentoo Packages | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Berend Dekens
2009-05-28 00:26:41 UTC
On the topic of invalid markup, in wordpressbuggy.cpp the generated struct should be enclosed in a <value> element. I reported this on the Bilbo forum as well as they currently use a forked version of KBlog. In wordpressbuggy.cpp on line 78 change: xmlMarkup += "<param><struct>"; into: xmlMarkup += "<param><value><struct>"; On line 123: xmlMarkup += "</member></struct></param>"; into: xmlMarkup += "</member></struct></value></param>"; In line 177: xmlMarkup += "<param><struct>"; into xmlMarkup += "<param><value><struct>"; And on line 227: xmlMarkup += "</member></struct></param>"; into xmlMarkup += "</member></struct></value></param>"; The resulting XML is now XML-RPC compliant. This does not solve the category error in the metaWeblog API but since wordpressbuggy.cpp generates its own XML, it does not seem to share the functionality that metaweblog.cpp uses. The result is that the WordPress API generates the correct category syntax while the metaWeblog API does not. Or should I open a seperate bug report for the suggested fix for wordpressbuggy.cpp? Any updates on this? KDE 4.4 is about to be released and my Blogilo 4.3.98 is throwing the same errors as before... Should be fixed for 4.4.1 and 4.5. WordpressBuggy should be already fixed but for all other APIs which use kxmlrpcclient I have not fixed it there. I mean of course that I have fixed it there (in kxmlrpcclient), sorry. This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of kdepim (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months. Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input. |