Hi, > Instead of calling a method, the new AUTH_USERDATA_CHANGE event is > triggered. The event gets the action (create, modify, delete), the "old" and > the "new" user data as event data. And an action plugin could do the > logging. I can imagine other uses and plugins for this new event: > > An alternative to this would be changing the auth class system from > inheritance to composition: The current auth class API remains, but there is > one auth class that dispatches the api call to various auth adapters. While > I am certainly able to do such a change, I won't do it without having the OK > from the community. Couldn't we combine this? We change our code to call $auth->triggerUserMod($type,...) which is a method of auth_basic and would wrap around $this->createUser and so on... Andi -- splitbrain.org -- DokuWiki mailing list - more info at http://wiki.splitbrain.org/wiki:mailinglist