Issue with ecto and publishing an edit

[electroteque]

Hi there, Ive discovered a problem when publishing an edit, ie the record is already published and making an edit to it. What has happened is sometimes it never updated, and other times i gets replaced somehow. To explain I edited a record of id 35 which is one just before the lastest record of id 36. It removed the latest record from the blog for some reason but its still in the system ?

Here is the response , well part of the response

Response:
<br />
<b>Warning</b>: Header may not contain more than a single header, new line detected. in <b>/Volumes/FIREWIRE/www/dev/weblog/plugins/serendipity_event_xmlrpc/PEAR/XML/RPC/Server.php</b> on line <b>395</b><br />

[garvinhicking]

PHP 4.4.2 and 5.1.2 contain a BC-breaking patch that breaks the PEAR XMLRPC library. You'll need to update the XMLRPC library by either downloading the new pear files, or better, downloading the xmlrpc library fiels from here:

http://cvs.sourceforge.net/viewcvs.py/* ... Server.php

Regards,
Garvin

[electroteque]

Ok thanks, I already have these updated pear packages, do i simply copy them over or are these packages been patched and cuzstomised a little ?

[electroteque]

Ok it looks like moving overmy updated pear classes of XML_RPC worked I had to add this though

if (!class_exists('XML_RPC_Base')) {
require_once dirname(__FILE__) . '/../RPC.php';
}

Myabe it could be an idea, for some upgrader of pear software in the admin system and apply the patches supplied for each plugin as it looks like non standard modifications have been added to it ?

It also looks like making edits and updates changes the blog date , i guess there is nothing i can do about that ? I keep trying to change the date for the entry in ecto but still not working.

[garvinhicking]

Hi!

Usually by just downloading or upgrading the XMLRPC plugin you should get the upgraded PEAR library for that plugin...a function to patch up original PEAR files with our custom mods is troublesome, because a patch might not be applicable in a forward-compatible way.

As for updating the blog date, I'm afraid that ecto submits the timestamp of an entry not the way it received it, but with an updated timestamp. Serendipity can only take what it gets submitted for the timestamp of an entry, so you can maybe look out for a function that tells ecto to not send an updated timestamp?

Best regards
,Garvin