From joseph at randomnetworks.com Thu Apr 3 21:47:29 2008 From: joseph at randomnetworks.com (Joseph Scott) Date: Thu, 3 Apr 2008 15:47:29 -0600 Subject: [wp-xmlrpc] small change to the way works Message-ID: <7E386CCC-63D6-4AB9-982F-3D763242AE95@randomnetworks.com> A small change has gone into -trunk in the way that XML-RPC handles for posts. The new behavior should more closely match the way that works in wp-admin. All it does is remove the new lines that were hard coded around in the XML-RPC code. http://trac.wordpress.org/ticket/6016 This will be in 2.6, but not 2.5.x releases. -- Joseph Scott joseph at randomnetworks.com http://joseph.randomnetworks.com/ From joseph at randomnetworks.com Mon Apr 7 18:42:10 2008 From: joseph at randomnetworks.com (Joseph Scott) Date: Mon, 7 Apr 2008 12:42:10 -0600 Subject: [wp-xmlrpc] wrapping faultstring value with CDATA In-Reply-To: References: <67131C5C-576E-439E-BF3B-E5208AF44664@randomnetworks.com> Message-ID: On Jan 14, 2008, at 9:51 AM, Joseph Scott wrote: > On Jan 14, 2008, at 9:23 AM, Joe Cheng wrote: > >> Is $this->message XML-escaped today? What happens, for example, if >> the error message contains the '&' character--will it be properly >> escaped to "&"? > > My gut response was going to be yes, but then I tried it. Turns > out the answer is no :-( > > I've created a ticket for this issue: http://trac.wordpress.org/ > ticket/5666 Following up on this issue, Ryan has committed this change to -trunk and the 2.5 branch, so we'll see this in any 2.5.x releases and 2.6. -- Joseph Scott joseph at randomnetworks.com http://joseph.randomnetworks.com/ From yahoo2 at yarrowsoft.com Thu Apr 10 16:40:20 2008 From: yahoo2 at yarrowsoft.com (Vladimir Yushko) Date: Thu, 10 Apr 2008 20:40:20 +0400 Subject: [wp-xmlrpc] API for remote access to comments Message-ID: <001101c89b29$ddb15550$7e4d14ac@nota> Hello! I developed comment client for WordPress. Comment client is administrative tool for manage comments. First upload to your blog xml-rpc server: http://commentclient.com/download/xmlrpc-comments.php After install client (all Windows platforms supports, 1.6Mb): http://commentclient.com/download/wpcommentclientsetup.exe I need help and feedback. Please tell me about my software. -- Best regards, Vladimir Yushko http://commentclient.com/ From joseph at randomnetworks.com Thu Apr 10 19:03:53 2008 From: joseph at randomnetworks.com (Joseph Scott) Date: Thu, 10 Apr 2008 13:03:53 -0600 Subject: [wp-xmlrpc] API for remote access to comments In-Reply-To: <001101c89b29$ddb15550$7e4d14ac@nota> References: <001101c89b29$ddb15550$7e4d14ac@nota> Message-ID: On Apr 10, 2008, at 10:40 AM, Vladimir Yushko wrote: > I developed comment client for WordPress. Comment client is > administrative > tool for manage comments. First upload to your blog xml-rpc server: > http://commentclient.com/download/xmlrpc-comments.php > > After install client (all Windows platforms supports, 1.6Mb): > http://commentclient.com/download/wpcommentclientsetup.exe > > I need help and feedback. Please tell me about my software. Providing a way to manage comments via XML-RPC is something that we've talked about before, so one of these days it will make it into the core WordPress code. We haven't really talked much about API specifics yet though. When I get a chance I'll take a look at your xmlrpc-comments.php file. -- Joseph Scott joseph at randomnetworks.com http://joseph.randomnetworks.com/ From joseph at randomnetworks.com Sun Apr 13 05:44:23 2008 From: joseph at randomnetworks.com (Joseph Scott) Date: Sat, 12 Apr 2008 23:44:23 -0600 Subject: [wp-xmlrpc] Problems with dateCreated in metaWeblog.newPost/editPost Message-ID: Ticket 6612 ( http://trac.wordpress.org/ticket/6612 ) points to a blog post ( http://www.franzone.com/2007/07/30/wordpress-xml-rpc- patch-for-metweblog-newpost-method/ ) that details a problem with the dateCreated field in metaWeblog.newPost/editPost. I was rather surprised to confirm this bug as detailed in the post. I figured if we'd had this problem for so long, one of the blog client authors would have complained about it before now :-) I've attached a simple patch to the ticket that addresses this issue. But date/time fields are particularly fragile in the current blog APIs, so I'd really like to get some feed back from folks in the field who have to deal with this before pressing forward. -- Joseph Scott joseph at randomnetworks.com http://joseph.randomnetworks.com/ From jalkut at red-sweater.com Sun Apr 13 06:33:50 2008 From: jalkut at red-sweater.com (Daniel Jalkut) Date: Sun, 13 Apr 2008 02:33:50 -0400 Subject: [wp-xmlrpc] Problems with dateCreated in metaWeblog.newPost/editPost In-Reply-To: References: Message-ID: <438703AF-BC49-4C7D-AC35-51CABF1DB9F8@red-sweater.com> Joseph, I think your instinct to be skeptical because of the lack of complaints among blog clients, is correct. Have you confirmed the problem? I just tested with MarsEdit and setting a date on a new post seems fine, with a cargo like: dateCreated 20080414T06:27:14Z There may be something nuanced that is wrong with the API, but it's not affecting me. I suspect it's not affecting other clients, either. I haven't looked closely at the fix that the bug reporter is proposing. As long as it doesn't break the current working behavior I'm not opposed to it. Daniel On Apr 13, 2008, at 1:44 AM, Joseph Scott wrote: > > Ticket 6612 ( http://trac.wordpress.org/ticket/6612 ) points to a > blog post ( http://www.franzone.com/2007/07/30/wordpress-xml-rpc-patch-for-metweblog-newpost-method/ > ) that details a problem with the dateCreated field in > metaWeblog.newPost/editPost. > > I was rather surprised to confirm this bug as detailed in the post. > I figured if we'd had this problem for so long, one of the blog > client authors would have complained about it before now :-) > > I've attached a simple patch to the ticket that addresses this > issue. But date/time fields are particularly fragile in the current > blog APIs, so I'd really like to get some feed back from folks in > the field who have to deal with this before pressing forward. > > -- > Joseph Scott > joseph at randomnetworks.com > http://joseph.randomnetworks.com/ > > > > _______________________________________________ > wp-xmlrpc mailing list > wp-xmlrpc at lists.automattic.com > http://lists.automattic.com/mailman/listinfo/wp-xmlrpc From joseph at randomnetworks.com Sun Apr 13 07:02:53 2008 From: joseph at randomnetworks.com (Joseph Scott) Date: Sun, 13 Apr 2008 01:02:53 -0600 Subject: [wp-xmlrpc] Problems with dateCreated in metaWeblog.newPost/editPost In-Reply-To: <438703AF-BC49-4C7D-AC35-51CABF1DB9F8@red-sweater.com> References: <438703AF-BC49-4C7D-AC35-51CABF1DB9F8@red-sweater.com> Message-ID: On Apr 13, 2008, at 12:33 AM, Daniel Jalkut wrote: > Joseph, I think your instinct to be skeptical because of the lack > of complaints among blog clients, is correct. > > Have you confirmed the problem? I just tested with MarsEdit and > setting a date on a new post seems fine, with a cargo like: > > > dateCreated > 20080414T06:27:14Z value> > > > There may be something nuanced that is wrong with the API, but it's > not affecting me. I suspect it's not affecting other clients, > either. I haven't looked closely at the fix that the bug reporter > is proposing. As long as it doesn't break the current working > behavior I'm not opposed to it. Thanks Daniel. I suspect what was happening is that they were sending the date as a string instead of dateTime.iso8601. I'm not sure why I didn't think about that earlier. I'll follow up with the ticket on Monday. -- Joseph Scott joseph at randomnetworks.com http://joseph.randomnetworks.com/ From toby at simmonsconsulting.com Mon Apr 14 15:28:09 2008 From: toby at simmonsconsulting.com (Toby Simmons) Date: Mon, 14 Apr 2008 10:28:09 -0500 Subject: [wp-xmlrpc] Problems with dateCreated in metaWeblog.newPost/editPost In-Reply-To: References: <438703AF-BC49-4C7D-AC35-51CABF1DB9F8@red-sweater.com> Message-ID: <003201c89e44$254b0f60$6fe12e20$@com> Just to confirm, Zempt has no problems specifying a date in a new post with payload of with 2.5 off the shelf dateCreated 20080412T07:00:00Z ___________________________________ W. Tobias Simmons Simmons Consulting, Web Design and Marketing toby at simmonsconsulting.com http://www.simmonsconsulting.com Phone: 501.821.4230 / Fax: 501.244.4416 -----Original Message----- From: Joseph Scott [mailto:joseph at randomnetworks.com] Sent: Sunday, April 13, 2008 2:03 AM To: wp-xmlrpc at lists.automattic.com Subject: Re: [wp-xmlrpc] Problems with dateCreated in metaWeblog.newPost/editPost On Apr 13, 2008, at 12:33 AM, Daniel Jalkut wrote: > Joseph, I think your instinct to be skeptical because of the lack > of complaints among blog clients, is correct. > > Have you confirmed the problem? I just tested with MarsEdit and > setting a date on a new post seems fine, with a cargo like: > > > dateCreated > 20080414T06:27:14Z value> > > > There may be something nuanced that is wrong with the API, but it's > not affecting me. I suspect it's not affecting other clients, > either. I haven't looked closely at the fix that the bug reporter > is proposing. As long as it doesn't break the current working > behavior I'm not opposed to it. Thanks Daniel. I suspect what was happening is that they were sending the date as a string instead of dateTime.iso8601. I'm not sure why I didn't think about that earlier. I'll follow up with the ticket on Monday. -- Joseph Scott joseph at randomnetworks.com http://joseph.randomnetworks.com/ From joseph at randomnetworks.com Wed Apr 16 03:49:25 2008 From: joseph at randomnetworks.com (Joseph Scott) Date: Tue, 15 Apr 2008 21:49:25 -0600 Subject: [wp-xmlrpc] exif warnings in XML-RPC responses Message-ID: <3A70670E-666B-42C2-BBB0-6F3866F666C2@randomnetworks.com> Some of you may have run into malformed XML-RPC responses from 2.5 blogs because of an image processing function (exif). http://trac.wordpress.org/ticket/6571 This is just a heads up that issue has been addressed in -trunk and the 2.5 branch. -- Joseph Scott joseph at randomnetworks.com http://joseph.randomnetworks.com/ From joseph at randomnetworks.com Fri Apr 25 20:07:07 2008 From: joseph at randomnetworks.com (Joseph Scott) Date: Fri, 25 Apr 2008 14:07:07 -0600 Subject: [wp-xmlrpc] WordPress 2.5.1 Message-ID: WordPress 2.5.1 was released this morning: http://wordpress.org/development/2008/04/wordpress-251/ There are two XML-RPC specific fixes in this release: faultString in xmlrpc responses is not properly escaped http://trac.wordpress.org/ticket/5666 Warnings from EXIF reader cause malformed XMLRPC responses http://trac.wordpress.org/ticket/6571 -- Joseph Scott joseph at randomnetworks.com http://joseph.randomnetworks.com/ From jalkut at red-sweater.com Fri Apr 25 20:08:29 2008 From: jalkut at red-sweater.com (Daniel Jalkut) Date: Fri, 25 Apr 2008 16:08:29 -0400 Subject: [wp-xmlrpc] WordPress 2.5.1 In-Reply-To: References: Message-ID: <57D887CE-9E20-4F7D-9E6D-DFF2FC38EC46@red-sweater.com> Awesome! On Apr 25, 2008, at 4:07 PM, Joseph Scott wrote: > > WordPress 2.5.1 was released this morning: > > http://wordpress.org/development/2008/04/wordpress-251/ > > There are two XML-RPC specific fixes in this release: > > faultString in xmlrpc responses is not properly escaped > http://trac.wordpress.org/ticket/5666 > > Warnings from EXIF reader cause malformed XMLRPC responses > http://trac.wordpress.org/ticket/6571 > > > > -- > Joseph Scott > joseph at randomnetworks.com > http://joseph.randomnetworks.com/ > > > > > _______________________________________________ > wp-xmlrpc mailing list > wp-xmlrpc at lists.automattic.com > http://lists.automattic.com/mailman/listinfo/wp-xmlrpc From joseph at randomnetworks.com Mon Apr 28 20:41:59 2008 From: joseph at randomnetworks.com (Joseph Scott) Date: Mon, 28 Apr 2008 14:41:59 -0600 Subject: [wp-xmlrpc] enclosure support for metaWeblog.newPost/editPost Message-ID: <5332CABB-D45C-4B80-97CE-853D089BC119@randomnetworks.com> Support for the enclosure element in metaWeblog.newPost/editPost was added to -trunk today: http://trac.wordpress.org/ticket/3405 http://trac.wordpress.org/changeset/7847 Please test this out and let us know if there are any issues. This will be part of the 2.6 release, so we'd like to have any problems with enclosures via XML-RPC resolved before then. -- Joseph Scott joseph at randomnetworks.com http://joseph.randomnetworks.com/