thanks, i'll try that.

On 8 Lug, 18:28, mbavio <[EMAIL PROTECTED]> wrote:
> This topic has to have at least 100 threads in this group. I wonder
> why dont you just search before starting a new one. It would be faster
> for you, and better for the quality of the group...
>
> Anyway, I´m going to answer you. There are some things that you can do
> with ACL, but it´s not the best tool always. For example, in this
> case. Instead of creating an gigantic tree of ACOS, why dont you add a
> new user_id row to your "creations" db with, and then you can check it
> jusr using the User session id. It´s much simpler, and way faster.
>
> Cheers,
> mbavio
>
> On Jul 8, 7:50 am, Paolo <[EMAIL PROTECTED]> wrote:
>
> > Ok, so I have to add the user id to every row right?
>
> > On 7 Lug, 23:43, francky06l <[EMAIL PROTECTED]> wrote:
>
> > > This is exactly ACL. User/creator will be an ARO and the "row" will be
> > > an ACO, the rest is permissions on CRUD operations.
>
> > > Now if it's just to limit the user/creator to "edit" the record AND if
> > > the creator/user_id is in the row, checking the user/creator_id of the
> > > row against the logged in user (in Session) can be done in edit
> > > action ..(without ACL).
>
> > > On Jul 7, 6:10 pm, Paolo <[EMAIL PROTECTED]> wrote:
>
> > > > Hi,
>
> > > > I need to know if it is possible by using cake ACL to allow
> > > > modifications to a single row only to the original creator of that
> > > > row. I'm not sure if also visibility is limited to the creator, but
> > > > modification would be fine for the moment. Should I create something
> > > > on my own or is it already possible with cake ACL?
>
> > > > thanks
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"CakePHP" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/cake-php?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to