You know, I've been struggling with this too.
Not really struggling, as, hell, you can code up something that will
work for one set of variables pretty easy, but making a general deal
that's flexible and whatnot? Harder.
I'm leaning pretty heavy towards AOP and business object level permissions.
> -Original Message-
> From: Mike Kear [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, June 17, 2008 6:52 PM
> To: CF-Talk
> Subject: Re: Looking for advice on permissions
>
> Thanks for your suggestions Claude. Perhaps i should give you a bit
> more background to
Thanks Gerald, I'll go have a look at that reference.
Cheers
Mike Kear
Windsor, NSW, Australia
Adobe Certified Advanced ColdFusion Developer
AFP Webworks
http://afpwebworks.com
ColdFusion, PHP, ASP, ASP.NET hosting from AUD$15/month
On Tue, Jun 17, 2008 at 6:58 AM, Gerald Guido <[EMAIL PROTECTE
Thanks for your suggestions Claude. Perhaps i should give you a bit
more background to this project. Just to clarify, the scenario is
about the opposite to the one you are puzzled by. I see the
circumstances where we might want to allow someone to edit content,
but for safety's sake not delet
IMHO, independant permissions for viewing, adding, editing, deleting
elements
may be going too much into details and obviously adding to the complexity.
Having only one permission for each type of element should be enough.
- any one can view elements on the public site anyway, so no permission
i
I don't have an answer but I can point you in a direction of a possible
option.
Take a look at this:
http://photos.guidofamily.org/grid.PNG
We need to do some fine grained permissions. Not nearly as fine grained as
your require. But I can see adding other edit/permissions options to the
drop down
6 matches
Mail list logo
