【问题标题】:Can't mass-assign protected attributes but attr_accessible is used无法批量分配受保护的属性,但使用了 attr_accessible
【发布时间】:2013-06-24 21:16:51
【问题描述】:

我收到以下错误:

无法批量分配受保护的属性:管理员、学生

当我使用以下 seed.rb 文件运行 rake db:seed 命令时:

roles = [
    Admin: 'Unlimited Access',
    Student: 'Default user role for each user created by sign-in interface.'
]

roles.each do |role, description|
  SecurityUsersRole.find_or_create_by_role_and_description(role,description)
end

我的模型的样子:

class SecurityUsersRole < ActiveRecord::Base

  # Accessible columns
  attr_accessible :description,
                  :role

  # Relationships
  ...

  # Validations
  validates :description, presence: true, length: { in: 4..32 }, uniqueness: true
  validates :role, length: {  maximum: 256 }, presence: true

end

我已经阅读了很多关于此的内容,似乎对于最新的 Rails 版本 Mass Assignment 如果关闭以防止黑客像这样攻击:

def signup
  params[:user] # => {:name => “ow3ned”, :admin => true}
  @user = User.new(params[:user])
end

关于这个有很多这样的问题,答案总是将 attr_accessible 设置为字段,但我已经这样做了。

编辑:

如果我使用以下语法({} 而不是 []),则添加第一对:

roles = {
    Admin: 'Unlimited Access',
    Student: 'Default user role for each user created by sign-in interface.'
}

如果我这样做,什么都不会改变:

SecurityUsersRole.find_or_create_by_role_and_description('Admin','Unlimited Access')
SecurityUsersRole.find_or_create_by_role_and_description('Student','Default user role for each user created by sign-in interface.')

经过一番阅读,find_or_create_by 助手似乎是depreciated 在 Rails 4.0 中。我正在使用 Rails 3.2,但也决定尝试其他技术:

roles = {
    Admin: 'Unlimited Access',
    Student: 'Default user role for each user created by sign-in interface.',
    Test:'wtf'
}

roles.each do |role, description|
  SecurityUsersRole.where(role:role,description:description).first_or_create
  #puts role
  #puts description
end

上面的语句仍然只创​​建第一条记录。我决定在 Rails 控制台中执行该语句,这是我得到的输出:

  SecurityUsersRole Load (5.0ms)  SELECT security_users_roles.* FROM security_users_roles WHERE security_users_roles.role = 'Admin' AND security_users_roles.description = 'Unlimited Access' FETCH FIRST ROW ONLY
  SecurityUsersRole Load (3.0ms)  SELECT security_users_roles.* FROM security_users_roles WHERE security_users_roles.role = 'Student' AND security_users_roles.description = 'Default user role for each user created by sign-in interface.' FETCH FIRST ROW ONLY
  SecurityUsersRole Exists (1.0ms)  SELECT 1 AS one FROM security_users_roles WHERE security_users_roles.description = 'Default user role for each user created by sign-in interface.' FETCH FIRST ROW ONLY
  SecurityUsersRole Load (1.0ms)  SELECT security_users_roles.* FROM security_users_roles WHERE security_users_roles.role = 'Test' AND security_users_roles.description = 'wtf' FETCH FIRST ROW ONLY
  SecurityUsersRole Exists (1.0ms)  SELECT 1 AS one FROM security_users_roles WHERE security_users_roles.description = 'wtf' FETCH FIRST ROW ONLY
=> {:Admin=>"Unlimited Access", :Student=>"Default user role for each user created by sign-in interface.", :Test=>"wtf"}

我无法理解到底发生了什么,但从控制台中选择所有用户只会返回第一个。那么,如果搜索其他角色,为什么不创建它们,因为它们不存在?

谁能建议我可以尝试什么?

【问题讨论】:

  • 尝试按如下方式设置您的角色哈希:roles = { Admin: 'Unlimited', Student: 'Default' }。意思是,使用大括号而不是方括号,否则你将在数组中有一个散列。
  • @mmichael 如果我使用 {} 括号,则只插入第一对 - 键值。这就是为什么我尝试在数组中保存值。

标签: ruby-on-rails-3 mass-assignment


【解决方案1】:

问题是由我的模型验证规则引起的,其中

  # Validations
  validates :description, presence: true, length: { in: 4..32 }, uniqueness: true
  validates :role, length: {  maximum: 256 }, presence: true

应该是

  # Validations
  validates :role, presence: true, length: { in: 4..32 }, uniqueness: true
  validates :description, length: {  maximum: 256 }, presence: true

我更改了 :role 和 :description 字段的位置。因此,rake db:seed 命令插入第一条记录,但第二条记录出现错误,插入被中止。结果是我总是导入第一条记录。

为了在使用种子时出现验证错误,您应该使用 !method 版本,如下所示:

SecurityUsersRole.where(role:role,description:description).first_or_create!

【讨论】:

    猜你喜欢
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 2011-09-04
    • 1970-01-01
    相关资源
    最近更新 更多