If it's *only* a question of obscurity in order to clean up the interface, you could hide them using CSS and avoid a bunch of logic in the view to determine what should be output. Just add a class to the body (or nav div, etc) based on the user group. Then, lay out some style rules to hide certain links for certain groups.
Of course, you'd need to set an ID on each link. And this method would probably demand some upkeep. Unless you used Cake to output that particular bit of CSS ... On Fri, Nov 14, 2008 at 12:08 PM, dr. Hannibal Lecter <[EMAIL PROTECTED]>wrote: > > Hi all, > > I'm halfway through the ACL implementation (well, almost...), and I > was wondering: is it better to hide the links which are denied by ACL > (we're talking about the already logged-in user), or show them and > give the user the Auth message "not enough privileges"? > > Obviously, hiding all the denied links will make views a bit messier > and slower to run overall, but user interface will be cleaner. Do you > think it's worth it? > > Please note that I'm not talking just about the admin/regular user > views, I'm talking about custom user groups *and* dynamic permissions. > > If you have an opinion, I'd like to hear it! > > Thanks in advance! > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
