Thursday, January 10, 2013

Best practice for naming ACOs in Cake?

Hi

Ive implemented a complete ACL-Solution in my app. I am using an administration form for acl-management (allow/deny) which I am building directly "on-the-fly" (from the aco-table).

So now, I would like to make this "acl-form" accessible to some groups with non-technical knowledge. Of course displaying the "default" method aliases to the user is not so self-explanatory for everyone. I would like to add a real name and a description.

What do you think were I should store this information for the aco? Modifying/extend the cake aco-table? Or in a related table? Which is most cake-like? In an optimum way the description and the name is related to the translateable behaviour to offer different languages.

Has somebody done this already?

Thanks for your input!

Regards,
Frank

--
Like Us on FaceBook https://www.facebook.com/CakePHP
Find us on Twitter http://twitter.com/CakePHP
 
---
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 cake-php+unsubscribe@googlegroups.com.
Visit this group at http://groups.google.com/group/cake-php?hl=en.
 
 

0 Comments:

Post a Comment

Subscribe to Post Comments [Atom]

<< Home


Real Estate