Hi Jeff, Thanks for having a look at the CAF and for the suggestions!
> Make this so that a runmode can be run with or without authentication. This very near our top priority at the moment. I do know how to do make this work, but I just have to get the time to add the feature. > So what I did was made a runmode called 'viewmonth' and 'a_viewmonth' > to list booked dates. If the run mode is prefixed iwth a_ then the > user must be authenticated or is auto forwarded to a login screen. One of the things we've been investigating is switching to Cees's prototype Auth plugin - cross porting the features from both auth systems into each other and ending up with a single CAP::Auth plugin. Cees's Auth plugin allows for runmode level authorization as well as just basic authentication. You can set it up so that anyone can view runmode_a, but only "managers" can view runmode_x. > This allows me to use the same code to render 2 pages. Maybe for the > future of CAF you could add the ability of "logged in" to be optional > for a runmode. This is definitely on the list as an intermediate solution before we try the full CAP::Auth stuff. Michael ----------------------------------------------------------------------- Michael Graham <[EMAIL PROTECTED]> YAPC::NA 2005 Toronto - http://www.yapc.org/America/ - [EMAIL PROTECTED] ----------------------------------------------------------------------- --------------------------------------------------------------------- Web Archive: http://www.mail-archive.com/[email protected]/ http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2 To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
