Thanks Darby, So you mean I dont need a single field in my db structure....but its confusing how this plugin is managing some complex kind of acl like I want to restrict some people from accessing a particular record, deleting a record and updating a record...let say I have scenario Model(Lead)---->Record(Xdocs) (there is a polymorphic association between these two) (Xdocs)
Read rights = admin,user 1,user 2,user 3 ....etc Write rights = admin,user 1,user 2,user 3 ....etc Update rights =admin, author Delete rights = admin,author how your plugin is managing all these things? without any database interaction? And I am using restful_authentication ..so I have that @current_user as well.. Thanks, Shahroon On Wed, Jun 10, 2009 at 5:58 PM, Matt Darby <m...@matt-darby.com> wrote: > > On Jun 9, 9:09 am, shahroon ali <shahroon....@gmail.com> wrote: > > Hi All, > > I am going to use restful_acl in my application on every record > in > > simple words i want to implement record based acl. I explored restful_acl > > and I applied it too, but so for I am not successful in doing so. > > I have question regarding restful_acl > > Does this plugin (now gem) needs any backend (database) configurations? > if > > yes then what kind of database structure? I just need a table structure > > > > Thanks, > > > > Shahroon > > > RESTful_ACL doesn't require any database setup. It's only requirement > is the existence of a @current_user variable, normally set by > something like restful_authentication. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
