CODEWITHSUNDEEP
phpmodel-view-controllercakephpcontroller
Brian
Brian

Reputation: 2147

Proper use of controllers with MVC (CakePHP)

Cake's documentation says "Most commonly, controllers are used to manage the logic for a single model." I'm finding this is uncommon for most of my code, and I don't want to break convention unless it is proper to do so.

For example, my application sends a user to their account dashboard after they log in - this uses data from probably half a dozen tables, not all of which are even related. Do I create a "dashboard" controller for this (even though there is no dashboard model or table)? Or do I create a dashboard method in an existing controller?

Thanks, Brian

Upvotes: 2

Views: 346

Answers (1)

8vius
8vius

Reputation: 5836

I have a similar situation and how I handle it is keeping the actions that connect a lot of models in the controller that is the most centric. For instance, my user can create voicenotes, comments, has settings, has twitter and facebook information. All this information I can get from my user model $this->User->Voicenotes->find('all'), for example.

I believe creating additional controllers might just confuse you, use what cake gives you, you can specify that models are to be used in a controller either by setting the $uses variable or using loadModel in the controller action, if you have your relations set up you can just do it the way i described before, no need to create additional controllers.

I guess it depends on how you want your own app to work and what comes easier in your situation.

Upvotes: 1

Related Questions