Further in the controller or view,give condition for only owner to be able to edit. Or u can give a column as user_id in the module table, to track the owner of the modules, but if u go for HABTM, u can nytime change the privileges for the users in the future.
On Wednesday, July 18, 2012 2:19:36 AM UTC+5:30, Andrew Johnston wrote:
Hello Again Everyone---I'm having a bit of trouble establishing my databases. To sum up my application, it allows users to make modules which then can be viewed by other users of the creator's choice.So I have:User hasMany Module <-- This is where I place the user id number of the creator of the moduleModule belongsTo UserUser HABTM Module <-- This table is only for those who are allowed to view the module, but don't own itBut I feel that this isn't the right way to do it. How should I implement this?Is it possible to do this solely in ACL? If so, how?Thanks to everyone in advance for their help!
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