On 3/6/06, Ezra Z. [email protected] wrote:
<%= link_to "Destroy" %> <% end %>
I updated to your latest code and this is working fine. I’m sure you
knew that, but there’s a field test for what it’s worth.
[snip – restrict_to isn’t DRY ]
No offense taken, I’m thick skinned
I see what you are talking
about now. I had never looked at the user engine before. It wouldn’t
be too hard at all to add something like this if you would use it.
Let me know and I can add a method for you. Also this weekend will be
the next release of a newer version of acl_system with a bunch more
functionality including individual model record protection.
If you wrote it, I’d use it and appreciate it greatly. I’m also very
interested in your new code coming this weekend.
Since you said that you hadn’t looked at UserEngine, here’s a couple
tidbits.
UserEngine has a Permissions class in addition to the Role and User.
A Permission is a combination of role, controller, and action. This
all gets stored in the database, so it’s only defined once. It’s not
as expressive as what you have, where you can easily combine roles
logically. But it seemed to be great for simple mappings of Role X
can do Action Y.
The two main helper methods were a big selling point for me though.
authorized?(:controller => ‘foo’, :action => ‘bar’)
link_if_authorized(“Some Page”, {:controller => ‘foo’, :action =>
‘bar’})
Thank you for what you’ve already done. This alone is enough to get
me started on plugging everything together.
– James