Where and how to assign a user :admin role for attr

You are using a lot of technical terminology in vague ways that is making your understanding of this process muddled, so I'm going to clear up some terminology first.

This is to protect against mass assignment as your link explains.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.

Where and how to assign a user :admin role for attr_accessible in rails 3.1?

Related Questions

Using Rails 3.1 :as => :admin for updating attributes protected by attr_accessible?

I solved the “Can't mass-assign protected attributes” adding the foreing key to attr_accessible, but I don't know if this is the correct way?

Rails and attr_accessible: is there a way to raise an exception if a non-mass-assignable attribute is mass-assigned?

Adding user to mongodb admin DB makes it impossible for me to use HTTP admin interface?

Conditional 'attr_accessible' using ActiveResource in Ruby on Rails?

Rails 3.1 attr_accessible verification receives an array of roles?