> One possibility here, to try to increase security without spending an > inordinate portion of development time on it, would be something like > this. Have a separate page on site for "who has access to what" with > things like vgifts, text messages, editing tags, etc. etc. each of which > can be set to everyone/registered users only/trusted only/trust filter > only/nobody. > > Then, when adding new features that might want to be restricted, just > add NewFeature to this page, and call hasPermision.NewFeature (or > whatever) to check permission.
I think this is very much now the new settings page works. Will have to ask Janine about it as she's the resident expert on it, but I believe it makes adding settings very easy. > I'm not a dev, so if this is either completely implausible or blindingly > obvious, feel free to beat me around the head with a large perl manual. :) Hey, we don't beat up our volunteers around here! ;) -- Mark Smith / xb95 [email protected] _______________________________________________ dw-discuss mailing list [email protected] http://lists.dwscoalition.org/cgi-bin/mailman/listinfo/dw-discuss
