Re: Best practices question

2010-01-08 Thread Foroct
Thank you that works like a charm. Usually when I write straight PHP I include an else statement but for some reason when doing this (my first cakePHP project) I did not do that. On Jan 8, 4:36 am, "Dr. Loboto" wrote: > Just a little additions: > >         // always have default value for acti

Re: Best practices question

2010-01-08 Thread Dr. Loboto
Just a little additions: // always have default value for action args to not receive "missing argument" errors function view($username = null) { if (!$username) { $this->Session->setFlash(__('Invalid User.', true)); $t

Re: Best Practices Question

2009-03-03 Thread keymaster
Have a look at this: http://groups.google.com/group/cake-php/browse_thread/thread/7638b690ae0545ff/53a804265793ace3?lnk=gst&q=crud# The more I think about it, the more sold I am on grigri's approach in the above thread. --~--~-~--~~~---~--~~ You received this mess

Re: Best Practices Question

2009-03-03 Thread keymaster
I'd define the following basic crud operations operations in appController to work generically independant of controller/model: add(), edit(), del(), view() admin_add(), admin_edit(), admin_del(), admin_view() Then, all your profile controllers would inherit from appController, and: delete_quot

Re: Best Practices Question

2009-03-03 Thread brian
I'd put as much as possible in its appropriate controller. And as much of the logic in the appropriate model. On Tue, Mar 3, 2009 at 4:47 PM, Dave Maharaj :: WidePixels.com wrote: > I have a controller USERS which displays a users profile. The profile data > is comprised of information from vari