I don't think you should put your admin functions in their own
controller.
First, having a separate admin controller means that, instead of just
loading one primary model per controller, you'll be stuck handling a
ton of models within that one controller, which could get messy and
almost
Hi Dave,
create an admin_controller and keep all admin functions separate from the
other controllers?
Personally I wouldn't. Have a look at the Cookbook source, this is
what I follow - all admin methods except special cases go in
app_controller, streamlines things a lot.
Cheers,
Jon
--
/ manageable
Thoughts on how to combat this?
-Original Message-
From: Jamie [mailto:jamie@gmail.com]
Sent: October-20-09 1:39 PM
To: CakePHP
Subject: Re: Admin Controller
I don't think you should put your admin functions in their own controller.
First, having a separate admin
tossing ideas around to
cleanit up and more readable / manageable
Thoughts on how to combat this?
-Original Message-
From: Jamie [mailto:jamie@gmail.com]
Sent: October-20-09 1:39 PM
To: CakePHP
Subject: Re: Admin Controller
I don't think you should put your admin functions
If this is going to be the only action in the controller, then I would
use the pages controller.
simply add an admin() function in the pages controller and use the
following route
$Route-connect('/admin', array('controller' = 'pages','action' =
'index'))
I think there is no magic to auto identify all the available admin actions.
What you are talking about would be kind of neat though...
Tijs
PaulV wrote:
Hi,
Having added CAKE_ADMIN functions to several controllers, I would like
to add an action somewhere so that I can go to the URL
