looks like the missing _parent-definition of prototype skin was the reason for helma returning the wrong href() (diff).

you were able to reproduce this? That would be bad news indeed.

that's an educated guess. i was just wondering why helma would produce "/" for the href() of a skin-object (instead of "/skins/[proto]/[name]", and the only way i could think of is a parent-problem. and then i figured out that there's no _parent-definition for skin-objects ... the whole thing explained: skin/delete.hac produces the confirm-page with a form embedded, but before the actual rendering it sets res.data.action = this.href(req.action); now if res.data.action is /delete (because of a parent-problem), the user has the right to remove a whole site, and she clicks on "delete" the site is gone. even worse that the confirm-page asks if she wants to delete just a skin ...

I think this happens when the skin's parent node (which is the per-protptype group node) has been evicted from cache while the URL is being built, and there's no _parent info available. In this case, getParent(), which is used to build the URL, returns null, resulting in a URL identical to that of the root object.

Now this is certainly a very very improbably case, although the probability that this happens seems very very small to me. I'll check it out.

I have to admit that I actually never READ the message. Only thing I can say is it had the usual length and the usual two buttons beneath. You know how it is...

It's IE6, and I'm running Norton Internet Security. After the erraneous doubleckick, the server tried to redirect to neger.antville.org/delete, which probably fits robert's theory.