Hello, I have a controller that handles subscriptions to articles. Add/edit/delete are publicly viewable actions, but there is a listSubscribers action that is called from the admin side of the site, and is not accessible to the public.
At the moment i simply change the layout and navigation within the action (so it renders the view in the admin layout, with the admin navigation, instead of the "public" layout and navigation), but am wondering if this is a smell that perhaps the method should be moved to it's own controller? Likewise, in my article controller, i have the standard crud methods for the admin side of the site, but also methods to view articles, for the public side of the site. Should there be "one controller that serves them all" irrespective of context, or should controllers be grouped according to functionality, as in all "public" controllers purely contain "public" methods, and functionality contained in a "public" controller that is to be accessed from the admin side should be removed and placed in it's own controller? -- View this message in context: http://zend-framework-community.634137.n4.nabble.com/Changing-layout-navigation-for-one-method-in-controller-tp2238322p2238322.html Sent from the Zend Framework mailing list archive at Nabble.com.
