@@ -424,7 +424,7 @@ Often we would like to initialise some aspect of our model based on who the `act belongs_to :owner, :class_name => "User" - after_user_new { |r| r.owner = acting_user } + after_user_new { |r| r.owner = r.acting_user } {.ruby} Note that `after_user_new` fires on both `user_new` and `user_create.` @@ -439,7 +439,7 @@ Other situations can be more complex, and the `:creator => true` shorthand may n class Event belongs_to :group - after_user_new { |event| event.group = acting_user.group } + after_user_new { |event| event.group = event.acting_user.group } end {.ruby} @@ -455,7 +455,7 @@ This definition says that a user can only create an event in their own group. When we combine the two... - after_user_new { |event| event.group = acting_user.group } + after_user_new { |event| event.group = event.acting_user.group } def create_permitted? acting_user.group == group manual/permissions.markdown b184ee04fe1bc02e340737ac9bf4debc4b4c0405 Bryan Larsen bryan@larsen.st http://github.com/tablatom/hobocookbook/commit/5b9aa6d51d92a3e8c220fbc83bd9e0e0162d8437 5b9aa6d51d92a3e8c220fbc83bd9e0e0162d8437 2009-11-03T13:15:54-08:00 2009-11-03T13:15:54-08:00 Doc bug: In after_user_new, the acting_user is available on the record, not in self. 72f8b97f608c1390ea37efdb5821ae2225a7b61e Bryan Larsen bryan@larsen.st