I am a Mac-User blogging with the software ecto ( ecto.kung-foo.tv ) via metaWeblog-API on blogger.de (antville-based). While testing the new version of ecto (Beta-Status), I got in touch with the programmer as I had difficulties connecting to blogger.de using the

In responce, that's what he wrote and I hope this is the right place to let you know:

---start---quote---

Yeah, I see what's wrong. Here's what your server is returning:

<?xml version="1.0" encoding="ISO-8859-1"?> <methodResponse> <params> <param> <value> <array> <data> <value><struct> <member> <name>url <value>/ </member> <member> <name>blogid <value>powerbook </member> <member> <name>blogName <value>powerbook _ blog </member> </struct></value> </data> </array> </value> </param> </params> </methodResponse>

It's bad xml for XMLRPC. It should be:

<?xml version="1.0" encoding="ISO-8859-1"?> <methodResponse> <params> <param> <value> <array> <data> <value><struct> <member> <name>url</name> <value><string>/</string></value> </member> <member> <name>blogid</name> <value><string>powerbook</string></value> </member> <member> <name>blogName</name> <value><string>powerbook _ blog</string></value> </member> </struct></value> </data> </array> </value> </param> </params> </methodResponse>

It would also be nicer if the encoding was set as: <?xml version="1.0" encoding="UTF-8"?>

ISO-8859-1 is out of date.

---end---quote---

I use the the story.createtime as="editor" macro in my story editor skin. However, since the Antville upgrade I have been having problems with the createtime macro date and time. The createtime sets the story date to a future date under the following sequence everytime.

1. Add a story
2. Save offline your story
3. On the stories page, click view to get the story
4. To enter edit mode, click the edit link while viewing the story
5. save offline the story - date and time in future
6. In edit mode, createtime has a date and time in the future, which you cannot edit

It took me some time to narrow down the sequence of events. If I click edit on the stories page there is no problem - it only occurs when I go from view to edit in the story - this is my work around.

UpdateIt happens everytime you edit now - its only correct after the initial update