that would be cool! how 'bout it, wizard of rss? :-)

yes, rss might be the way. i just wonder how to create such an output: it could take some time to process a bigger weblog and turn every story, comment, image (...) data into an exchangable format. would a direct request via url work without time-out?

this is a clear case for the XML extension. It should/might be possible to dump or load the whole weblog contents with a few lines of code. Might be a good idea to consult StefanP on this.

@tobi: chances are good such a request dies with a timeout, although i never tested something like that. even if it does not, this would block one thread per export for a pretty long time ... @hns: yep, that sounds good!

would solve this blocking? or is this a job for the scheduler, anyway?

nope, using xml-extension is independent from the blocking/threading issue. I don't think we'll have a problem with timeouts though, I think it should be possible to dump the db content for big weblogs within seconds (with picture and goodie files going separate). Let's find out.

the xml-extension currently has two features:

• convert an xml-file in a specified way and make hopobjects out of it. this can easily be used to parse rss-output. the rss-output is done with skins.

• load/save in a generic helma-xml-style. with this function you can export HopObjects and re-create them exactly the way they were before (but you've got a lot of ugly helma-attributes in your xml-document). for real-world-use one thing has to be changed: at the moment you're only able to specify how many levels you want to descend into the object tree, but you can't completely suppress the output of certain nodes. so if you walk down weblog-owner-subscriptions-otherweblog-etc etc (don't know the exact structure) you'll eventually dump more than one weblog. this is not a lot of work, but requires some thoughts about the format of handing over this configuration. maybe you give the Xml.load/save functions a try and suggest sg.

As it is, Antville does provide permalinks to comments, but does so by linking to the story with an #anchor to the comment id. (The link you get in the recent mod list for comments). I think if offering a perma-link to comments (to which I'm +1), it should be this and not a page with the comment alone. The idea for doint it this way is that a comment relies on and should be viewed within its context (i.e. the thing it is commenting upon).

a comment relies on and should be viewed within its context

but that's obviously not the case anymore (i can view a comment attached to the wrong parent).

it's not a big issue but i think it not a big issue either to check if the url reflects the correct story/comments hierarchy.

i can view a comment attached to the wrong parent

that's a different problem than providing perma-links to comments, innit?

it's not a big issue but i think it not a big issue either to check if the url reflects the correct story/comments hierarchy.

I'd say it's a bug, right?

that's the problem i described with emphasis above. the permalink for comments was just a minor note at the end.

that's the problem i described with emphasis above.

which is clearly a bug so I didn't feel the need to comment further.

the permalink for comments was just a minor note at the end.

... to which I replied that we do have permalinks in the recent mods list already, and maybe just need a way to provide/expose them.

(just to make things clear ;-)

:)

no seriously, sometimes it's good to have a controlled dialogue.

i fixed the bug: if one calls main-action for a comment, he's getting redirected to story-main (with an anchor to the requested comment).

+1 for including permalink of comments in default skins

+1 from me too.

ok, then i'll do it.

hi. i have no idea how to post. i have used blogger before, but i got tired of it. however, this is very complex for me. can someone refer me to anyone or anything? thanks.

===skittleholic===