I repeat what I put in the other post, have you heard of ACL?
With a correct ACL tree, you can limit access depending on the role,
just like the thing that you wanna do. Of course, if for example you
have differente edits for different roles, then there is no ACL that
can help you. But with the s
Unless the different roles have access to totally different
functionality, I don't see why you'd want to do this.
It'd be much easier to have the form(s) customize themselves based on
what the user's role is - or better yet, implement an ACL tree to
cover all the different functionalities availab
> Since CakePHP 1.2 there is the possibility to define custom prefix
> routing, so it can be possible to do something like:
>
> Router::connect('/brokers/contract/edit', array('prefix' =>
> 'brokers'));
> Router::connect('/laywers/contract/edit', array('prefix' =>
> 'laywers'));
> Router::connect
On 2 jun, 14:20, Jaime <[EMAIL PROTECTED]> wrote:
> Cake's admin routes are nice, but are designed for a simpler scenario
> (Users vs. Admins), so won't help here.
Since CakePHP 1.2 there is the possibility to define custom prefix
routing, so it can be possible to do something like:
Router::conn
You might find this article interesting:
http://bakery.cakephp.org/articles/view/using-cake_admin-for-multiple-user-types
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"CakePHP" group.
To post to this group, send em
Hello everybody,
This topic is quite similar to
http://groups.google.com/group/cake-php/browse_thread/thread/35900a65ab04ab05/92b6e71a451c35d0?lnk=gst&q=roles
which remains still unresolved.
It's just about a common scenario while building a corporate Intranet.
There is a fine DB and many model
