sorry, but this tool was disabled already long ago. however, it would not have been ready to import blogger data to antville.org, only to the former hopdev.helma.org antville installation for testing purposes. nobody tested at that time so it went into one of the lower drawers.

thanks for the answer, tobi. i guess i have to do that manually then. there should be approximately 400 stories in the bloggerblog. but i would at least need to find a way to post stories with past timestamps. any pointers for that?

...is really easy.

andrea. du bist mein guter geist.

I updated root/bloggerapi.js and merged in the changes in app.properties. Unfortunately I can't try it out with w.bloggar right now because my windows box is currently running linux and compiling gcc, which may take another hour or two... I'll report later.

It somewhat works. However, in addition to root/bloggerapi.js, I had to update storymgr/securityFunctions.js, and I'm not at all sure this was a safe thing to do - function isDenied now takes an additional argument, and if it is called without it looks like it will return invalid results. On the other hand I don't want to update all of antville because I don't know if there is any untested code in there...

So, basic posting via w.bloggar now works, but please audit the partial update i did! Fully working blogger API will need a full(er) update of antville.org code.

BTW, w.bloggar also seems to support non-standard title and topics extensions to the Blogger API - this would be really fun to support in antville!

OK, I had to backpedal on that update. That means we'd have to do a full update, which I'm not confident enough to do.

But from what I saw, support for w.bloggar and other remote posting tools will be very cool, esp. with title/topics support, so this is very worth it!

while updating the blogger-api in antville i had to change nearly all security functions because i wanted to use the standard functions instead of duplicating functionality in the blogger-api methods. that's why nearly all securityfunctions need a second argument now (the permission-level). during my tests i didn't find any problems with that, so it should be safe to update antville.org to the current cvs state.

Blogger API works great now - thanks Robert! Even story titles are supported now for tools that wrap it within <title> tags, which seems to be the prevalent workaround (that's my contribution).

Unfortunately, "cvs -n update" announces some conflicts, so I don't feel comfortable to update antville.org without halting the server.

hi hannes, can you give me a small hint regarding the settings of w.bloggar, so that i can also test it with the latest CVS. i get a "invalid procedure call or argument"-error after trying to connect to the server for the first time. w.bloggar seems to be able to call getUsersBlogs() with no problems (i checked this by writing some stuff to the helma-log), but then just the above error is returned by w.bloggar. i am using the site-alias as the Account Alias, host is "localhost", page is "/helma/antville" and port is 8081. furthermore i'm using the Blogger API without template support. any clue of what i might be doing wrong? thanks.

I don't have access to w.bloggar right now because my win machine is running linux and doing a monster compile job (gcj again).

What is Antville returning? Is that the entire error message you get? If so, it seems to come from w.bloggar itself, maybe when parsing the result from getUsersBlogs() or when preparing to send a second XML-RPC request.

sorry for the bothering. it does work with the latest CVS. it just didn't work with my 'modified' version. it seems that i've broken sthg in my code. thanks anyways. btw: very very cool thing

one of the href's was broken in my database, that's why the strange error occured.

good to hear that it's working.