2008/7/10 The Editor <[EMAIL PROTECTED]>: > Though I'm no longer actively supporting ZAP, it's been able to do > this and much more for a long time.
I actually did take a look at ZAP and the MemberMgmt recipe before starting, but it's that "and much more" part that turned me away. By now, I know how PmWiki works; I've read through the code enough times to trust what it's doing. Admittedly Pm's code could do with more documentation aimed at developers and longer variable names, but it does all work and lets me pick which parts to enable or disable. ZAP, on the other hand, is a single monolithic recipe that proudly lists 30 different things that it does. The effort I'd need to put into understanding all of it exceeds the effort I'm putting into writing what I need myself. Since we're dealing with account management I figure I need to be extra careful with what I do. Essentially, I don't think I need generic form processing with extra features to enable account administration. Additionally, there are quite a few things that I need that I haven't seen ready solutions for. For example, I want to have <example.com/wiki/SomeUser> resolve to a default profile page for SomeUser that reads a template from somewhere and SomeUser's data from elsewhere. The tricky part (or at least one of them) is the lack of any default group for these profile pages. Another odd feature that I want is controlled, undoable deletion of other people's user accounts by non-administrators. Most of my sites are internal, and what with the restructuring and changing secretaries and other things, it's not always clear if someone's still an employee or not. And since keeping track of people really isn't my job, I figure I ought to make it possible for anyone to update these details. eemeli _______________________________________________ pmwiki-users mailing list [email protected] http://www.pmichaud.com/mailman/listinfo/pmwiki-users
