[wp-testers] Posts Don't Publish Via XML-RPC

Otto otto at ottodestruct.com
Mon Dec 15 16:11:29 GMT 2008


My guess would be that ScribeFire is sending a date/time that is
either wrong or that WordPress is not parsing correctly.


On Sat, Dec 13, 2008 at 8:57 AM, Kirk M <kmb42vt at gmail.com> wrote:
> Just for comparison purposes, I'm using the latest version of Windows Live
> Writer Beta as my main blog editor which also publishes using XML-RPC. I
> often "post as draft" and what you're seeing is not occurring when using
> WLW. ScribeFire might be sending some sort of incorrect data when posting as
> draft that isn't agreeing with 2.7. It wouldn't be the first time that's
> ever happened. I've used it off and on since it was called PFF and it's
> often gone funky on me.
>
> There's a recently updated version of ScribeFire (3.1.5). I load it up into
> FX 3.1 (nightly builds) later on today and see if I get the same thing
> you're seeing.
>
> On 12/13/2008 6:29 AM, Jeff Chandler wrote:
>>
>> I'm using ScribeFire and the built in support for XML-RPC.  Their are two
>> weird things going on and they are related. If I select the option to
>> publish the post as a draft, when I login to WordPress and edit the draft,
>> the Publish button will not be displayed and instead, it's replace with a
>> SCHEDULE button. If I save the post and play around with the settings, I can
>> get the SCHEDULE button to be replaced with the PUBLISH button.
>>
>> Just 5 minutes ago, I published the post bypassing the draft option from
>> scribefire. When I logged into the WordPress backend, the publish button was
>> gone an the post somehow was scheduled to be published. When I clicked on
>> the EDIT link to edit the post status, all I can choose is SCHEDULED,
>> PENDING, or DRAFT.
>>
>> I've clicked on the EDIT link and have reset the time for when the post
>> was scheduled and when I did that and then saved the changes, the post
>> status went to PUBLISHED.
>>
>> This seems like really weird behavior to me and I'm not sure if it's the
>> fault of WordPress, The XML-RPC or ScribeFires interaction with WP2.7.
>>
>> _______________________________________________
>> wp-testers mailing list
>> wp-testers at lists.automattic.com
>> http://lists.automattic.com/mailman/listinfo/wp-testers
>>
> _______________________________________________
> wp-testers mailing list
> wp-testers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-testers
>


More information about the wp-testers mailing list