Torben Nehmer wrote: >> >> - does $obj->parameter() observe the same rules as >>mgd_delete_article()? (hint: the documentation doesn't say a thing >>about it!) > > > Fact is, that the parameter function does not have to do any > consistency checking upon delete, because no other entity can be used > on parameters, so there are no dependencies. Also parameters inherit > access permissions from the parent object.
That's all I need to know to sleep easy tonight. Great! > What you can do before deletion is testing whether the user in question > is in the group required to delete something. If yes, commence, if no, > abort the whole thing before you come to it. But I'd like to get _into_ the functuion call and alter it. > The problem is, that the whole permission system of Midgard is rather > simple. That's a feature, not a bug ;) -- I don't mind the system being simple at all -- in fact is something I like. What I'd be able is to hook my own logic into mgd calls -- without having to reimplement them. But I am getting silly. > So changing anything there will require a lot of thought before > we do anything, especially because this is something we shuld keep for > the next major version upgrade of Midgard. No worries. No request for changes at all. > I'd suggest that you write a small specification of what you need and > then post it here on midgard-user to discuss it. Only then I can give > you a more elaborte answer on what should be easy, and what not. You've answered my doubts. I would guess a more PHP-based midgard -- like midgard lite can expose its hooks a lot more transparently. Objects can be inherited and "builtins" overriden more easily. That's what I'd like to have, but that's pie-in-the-sky. cheers, m --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
