Hi Vikram,in general any Action can live wherever it suits your taste. Security and required privileges are tied to the action itself and not to the module. So depending on your application both ways can make sense: if the admin interface only adds few features to an existing user interface it makes sense to place the actions in the same module(s). If the admin interface is very different (let's say for a shop application for example) it certainly makes sense to have a separate admin module.
There is an example for authentication and secure actions in the sample app, however there is no example for the use of the privilege system.
hope that helps felix On May 6, 2009, at 4:33 AM, [email protected] wrote:
Hi allIn my app, I have a Listing module which allows users to add new listings to the database (SaveAction). Administrators can update and delete these listings. I'm looking for some guidance on building this admin module - specifically starting with these questions:1. As a general rule, should admin actions be in a separate Admin module? Or can they coexist with user actions in the existing Listing module? If the latter, how do I restrict edit/delete actions only to administrators?2. Can anyone point me to some docs or public source code that implements an admin panel with login/logout and privileges?Thanks, Vikram _______________________________________________ users mailing list [email protected] http://lists.agavi.org/mailman/listinfo/users
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ users mailing list [email protected] http://lists.agavi.org/mailman/listinfo/users
