Here is a good little github project that provides ACL management
https://github.com/interlock/acl_plugin
Just read it up on the CakePHP book listed on that project, try out
the ACL+Auth setup on a dummy project first and then go ahead. Thats
what I would do.
On Apr 4, 12:13 am, adam_g2000 <a...@designcollective.co.nz> wrote:
> Hi All,
>
> I've been working on a project, that is essentially an artists
> portfolio. She's just dropped a bombshell, previously, the
> authentication was simple. You either had rights to view the site and
> it's CMS or you had the rights to view only the site.
>
> Now she wants to *lock* certain areas of the site, so that she can
> show some work, to only some people. So it sounds to me like I need to
> learn the ACL component. Or is that too complicated for what I'm
> doing?
>
> the site mainly consists of visual 'lists' of links to images (which
> are in a db of course). In a page of these links, I'm showing the
> whole list, within a controllers method. When we move forward, it may
> be that the method will need to show only some of these links based on
> the ACL, is this level of granularity possible, or does simple ACL
> stop at the method?
>
> Thanks in advance for any advice,
>
> Adam.
--
Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org
Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions.
To unsubscribe from this group, send email to
cake-php+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
No comments:
Post a Comment