blocks|key|1163105|text|在您的表单中，是否通过批量赋值传入了不属于您的用户模型或任何嵌套模型的任何其他属性？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1163106|如果是这样，我相信ActiveRecord::UnknownAttributeError在这个实例中被触发了。|1163107|否则，我认为你可以创建你自己的控制器，生成如下代码：|1163108|#+app/controllers/registrations_controller.rb
class+RegistrationsController+<+Devise::RegistrationsController
++def+new
++++super
++end

++def+create
++++#+add+custom+create+logic+here
++end

++def+update
++++super
++end
end+|code-block|syntax|javascript|1163109|然后使用以下命令告诉devise使用该控制器而不是默认控制器：|1163110|#+app/config/routes.rb
devise_for+:users,+:controllers+=>+{:registrations+=>+"registrations"}|1163111|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|S|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|T|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|N|5|H|7|V|8|@]|9|@]|A|$I|J]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

In your form are you passing in any other attributes, via mass assignment that don't belong to your user model, or any of the nested models?

If so, I believe the ActiveRecord::UnknownAttributeError is triggered in this instance.

Otherwise, I think you can just create your own controller, by generating something like this:

<pre><code># app/controllers/registrations_controller.rb
class RegistrationsController &lt; Devise::RegistrationsController
 def new
 super
 end

 def create
 # add custom create logic here
 end

 def update
 super
 end
end 
</code></pre>

And then tell devise to use that controller instead of the default with:

<pre><code># app/config/routes.rb
devise_for :users, :controllers =&gt; {:registrations =&gt; "registrations"}
</code></pre>

blocks|key|1163190|text|我相信有一个比重写RegistrationsController更好的解决方案。我做了完全相同的事情(我只是有组织而不是公司)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1163191|如果您正确地设置了模型和视图级别的嵌套表单，则一切工作起来都很有吸引力。|1163192|我的用户模型：|1163193|class+User+<+ActiveRecord::Base
++#+Include+default+devise+modules.+Others+available+are:
++#+:token_authenticatable,+:confirmable,+:lockable+and+:timeoutable
++devise+:database_authenticatable,+:registerable,
+++++:recoverable,+:rememberable,+:trackable,+:validatable

++has_many+:owned_organizations,+:class_name+=>+'Organization',+:foreign_key+=>+:owner_id

++has_many+:organization_memberships
++has_many+:organizations,+:through+=>+:organization_memberships

++#+Setup+accessible+(or+protected)+attributes+for+your+model
++attr_accessible+:email,+:password,+:password_confirmation,+:remember_me,+:name,+:username,+:owned_organizations_attributes

++accepts_nested_attributes_for+:owned_organizations
++...
end|code-block|syntax|javascript|1163194|我的组织模型：|1163195|class+Organization+<+ActiveRecord::Base
++belongs_to+:owner,+:class_name+=>+'User'
++has_many+:organization_memberships
++has_many+:users,+:through+=>+:organization_memberships
++has_many+:contracts

++attr_accessor+:plan_name

++after_create+:set_owner_membership,+:set_contract
++...
end|1163196|我的观点：'devise/registrations/new.html.erb‘|1163197|<h2>Sign+up</h2>

<%25+resource.owned_organizations.build+if+resource.owned_organizations.empty?+%25>
<%25=+form_for(resource,+:as+=>+resource_name,+:url+=>+registration_path(resource_name))+do+%7Cf%7C+%25>
++<%25=+devise_error_messages!+%25>

++<%25=+f.label+:name+%25><br+/>
++++<%25=+f.text_field+:name+%25>

++<%25=+f.label+:email+%25><br+/>
++++<%25=+f.text_field+:email+%25>

++<%25=+f.label+:username+%25><br+/>
++++<%25=+f.text_field+:username+%25>

++<%25=+f.label+:password+%25><br+/>
++++<%25=+f.password_field+:password+%25>

++<%25=+f.label+:password_confirmation+%25><br+/>
++++<%25=+f.password_field+:password_confirmation+%25>

++<%25=+f.fields_for+:owned_organizations+do+%7Corganization_form%7C+%25>

++++<%25=+organization_form.label+:name+%25><br+/>
++++++<%25=+organization_form.text_field+:name+%25>

++++<%25=+organization_form.label+:subdomain+%25><br+/>
++++++<%25=+organization_form.text_field+:subdomain+%25>

++++<%25=+organization_form.hidden_field+:plan_name,+:value+=>+params[:plan]+%25>

++<%25+end+%25>

++<%25=+f.submit+"Sign+up"+%25>
<%25+end+%25>

<%25=+render+:partial+=>+"devise/shared/links"+%25>|1163198|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|W|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|X|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|Y|8|@]|9|@]|A|$]]|$1|M|3|N|5|H|7|Z|8|@]|9|@]|A|$I|J]]|$1|O|3|P|5|6|7|10|8|@]|9|@]|A|$]]|$1|Q|3|R|5|H|7|11|8|@]|9|@]|A|$I|J]]|$1|S|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|T|$]]

I believe there is a better solution than rewrite the RegistrationsController. I did exactly the same thing (I just have Organization instead of Company).

If you set properly your nested form, at model and view level, everything works like a charm.

My User model:

<pre><code>class User &lt; ActiveRecord::Base
 # Include default devise modules. Others available are:
 # :token_authenticatable, :confirmable, :lockable and :timeoutable
 devise :database_authenticatable, :registerable,
 :recoverable, :rememberable, :trackable, :validatable

 has_many :owned_organizations, :class_name =&gt; 'Organization', :foreign_key =&gt; :owner_id

 has_many :organization_memberships
 has_many :organizations, :through =&gt; :organization_memberships

 # Setup accessible (or protected) attributes for your model
 attr_accessible :email, :password, :password_confirmation, :remember_me, :name, :username, :owned_organizations_attributes

 accepts_nested_attributes_for :owned_organizations
 ...
end
</code></pre>

My Organization Model:

<pre><code>class Organization &lt; ActiveRecord::Base
 belongs_to :owner, :class_name =&gt; 'User'
 has_many :organization_memberships
 has_many :users, :through =&gt; :organization_memberships
 has_many :contracts

 attr_accessor :plan_name

 after_create :set_owner_membership, :set_contract
 ...
end
</code></pre>

My view : 'devise/registrations/new.html.erb'

<pre><code>&lt;h2&gt;Sign up&lt;/h2&gt;

&lt;% resource.owned_organizations.build if resource.owned_organizations.empty? %&gt;
&lt;%= form_for(resource, :as =&gt; resource_name, :url =&gt; registration_path(resource_name)) do |f| %&gt;
 &lt;%= devise_error_messages! %&gt;

 &lt;p&gt;&lt;%= f.label :name %&gt;&lt;br /&gt;
 &lt;%= f.text_field :name %&gt;&lt;/p&gt;

 &lt;p&gt;&lt;%= f.label :email %&gt;&lt;br /&gt;
 &lt;%= f.text_field :email %&gt;&lt;/p&gt;

 &lt;p&gt;&lt;%= f.label :username %&gt;&lt;br /&gt;
 &lt;%= f.text_field :username %&gt;&lt;/p&gt;

 &lt;p&gt;&lt;%= f.label :password %&gt;&lt;br /&gt;
 &lt;%= f.password_field :password %&gt;&lt;/p&gt;

 &lt;p&gt;&lt;%= f.label :password_confirmation %&gt;&lt;br /&gt;
 &lt;%= f.password_field :password_confirmation %&gt;&lt;/p&gt;

 &lt;%= f.fields_for :owned_organizations do |organization_form| %&gt;

 &lt;p&gt;&lt;%= organization_form.label :name %&gt;&lt;br /&gt;
 &lt;%= organization_form.text_field :name %&gt;&lt;/p&gt;

 &lt;p&gt;&lt;%= organization_form.label :subdomain %&gt;&lt;br /&gt;
 &lt;%= organization_form.text_field :subdomain %&gt;&lt;/p&gt;

 &lt;%= organization_form.hidden_field :plan_name, :value =&gt; params[:plan] %&gt;

 &lt;% end %&gt;

 &lt;p&gt;&lt;%= f.submit "Sign up" %&gt;&lt;/p&gt;
&lt;% end %&gt;

&lt;%= render :partial =&gt; "devise/shared/links" %&gt;
</code></pre>

blocks|key|949154|text|使用名称空间覆盖设计控制器和视图的一种更好、更有组织的方式：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|949155|创建以下文件夹：|949156|app/controllers/my_devise
app/views/my_devise|code-block|syntax|javascript|949157|将您想要覆盖的所有控制器放入app/+controllers+/my_devise中，并将MyDevise命名空间添加到控制器类名称中。Registrations示例：|offset|length|style|CODE|949158|#+app/controllers/my_devise/registrations_controller.rb
class+MyDevise::RegistrationsController+<+Devise::RegistrationsController

++...

++def+create
++++#+add+custom+create+logic+here
++end

++...++++

end+|949159|相应地更改您的路由：|949160|devise_for+:users,
+++++++++++:controllers++=>+{
+++++++++++++:registrations+=>+'my_devise/registrations',
+++++++++++++#+...
+++++++++++}|949161|将所有需要的视图从Devise+gem文件夹复制到app/views/my_devise中，或者使用rails+generate+devise:views，删除未覆盖的视图，并将devise文件夹重命名为my_devise。|949162|这样，您就可以将所有内容整齐地组织到两个文件夹中。|949163|entityMap^0|0|0|0|19|8|1W|D|0|0|0|0|P|J|1E|R|2H|6|2U|9|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|12|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|13|8|@$K|14|L|15|M|N]|$K|16|L|17|M|N]]|9|@]|A|$]]|$1|O|3|P|5|F|7|18|8|@]|9|@]|A|$G|H]]|$1|Q|3|R|5|6|7|19|8|@]|9|@]|A|$]]|$1|S|3|T|5|F|7|1A|8|@]|9|@]|A|$G|H]]|$1|U|3|V|5|6|7|1B|8|@$K|1C|L|1D|M|N]|$K|1E|L|1F|M|N]|$K|1G|L|1H|M|N]|$K|1I|L|1J|M|N]]|9|@]|A|$]]|$1|W|3|X|5|6|7|1K|8|@]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|1L|8|@]|9|@]|A|$]]]|Z|$]]

A better and more organized way of overriding Devise controllers and views using namespaces:

Create the following folders: 

<pre><code>app/controllers/my_devise
app/views/my_devise
</code></pre>

Put all controllers that you want to override into app/controllers/my_devise and add <code>MyDevise</code> namespace to controller class names. <code>Registrations</code> example: 

<pre><code># app/controllers/my_devise/registrations_controller.rb
class MyDevise::RegistrationsController &lt; Devise::RegistrationsController

 ...

 def create
 # add custom create logic here
 end

 ... 

end 
</code></pre>

Change your routes accordingly:

<pre><code>devise_for :users,
 :controllers =&gt; {
 :registrations =&gt; 'my_devise/registrations',
 # ...
 }
</code></pre>

Copy all required views into <code>app/views/my_devise</code> from Devise gem folder or use <code>rails generate devise:views</code>, delete the views you are not overriding and rename <code>devise</code> folder to <code>my_devise</code>.

This way you will have everything neatly organized in two folders.

blocks|key|949221|text|您可以为设计定制生成视图和控制器。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|949222|使用|949223|rails+g+devise:controllers+users+-c=registrations|code-block|syntax|javascript|949224|和|949225|rails+g+devise:views+|949226|它会将特定的控制器和视图从gem复制到您的应用程序中。|949227|接下来，告诉路由器使用此控制器：|949228|devise_for+:users,+:controllers+=>+{:registrations+=>+"users/registrations"}|949229|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|W|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|X|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|Y|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|Z|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|10|8|@]|9|@]|A|$]]|$1|Q|3|R|5|F|7|11|8|@]|9|@]|A|$G|H]]|$1|S|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|T|$]]

You can generate views and controllers for devise customization.

Use

<pre><code>rails g devise:controllers users -c=registrations
</code></pre>

and

<pre><code>rails g devise:views 
</code></pre>

It will copy particular controllers and views from gem to your application.

Next, tell the router to use this controller:

<pre><code>devise_for :users, :controllers =&gt; {:registrations =&gt; "users/registrations"}
</code></pre>

blocks|key|949302|text|非常简单的方法只需转到终端，类型如下|type|unstyled|depth|inlineStyleRanges|entityRanges|data|949303|rails+g+devise:controllers+users+//This+will+create+devise+controllers+in+controllers/users+folder|code-block|syntax|javascript|949304|下一步是使用自定义视图|949305|rails+g+devise:views+users+//This+will+create+devise+views+in+views/users+folder|949306|现在在您的route.rb文件中|949307|devise_for+:users,+controllers:+{
+++++++++++:sessions+=>+"users/sessions",
+++++++++++:registrations+=>+"users/registrations"+}|949308|您还可以添加其他控制器。这将设计使用用户文件夹中的控制器和用户文件夹中的视图。|949309|现在，您可以根据需要自定义视图，并将逻辑添加到controllers/users文件夹中的控制器。享受吧！|949310|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|W|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|X|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|Y|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|Z|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|10|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|11|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|T|$]]

Very simple methods
Just go to the terminal and the type following

<pre><code>rails g devise:controllers users //This will create devise controllers in controllers/users folder
</code></pre>

Next to use custom views 

<pre><code>rails g devise:views users //This will create devise views in views/users folder
</code></pre>

now in your route.rb file

<pre><code>devise_for :users, controllers: {
 :sessions =&gt; "users/sessions",
 :registrations =&gt; "users/registrations" }
</code></pre>

You can add other controllers too. This will make devise to use controllers in users folder and views in users folder.

Now you can customize your views as your desire and add your logic to controllers in controllers/users folder. 
Enjoy !

I have added a field to the sign-up form that is based on a different model, see <a href="https://stackoverflow.com/questions/3544265/how-do-i-use-nested-attributes-with-the-devise-model">How do I use nested attributes with the devise model</a> for the gory details. This part is working fine.

The problem now is when I save, it is failing in the create action of the registrations controller that is supplied by devise with an <code>Activerecord::UnknownAttributeError</code> on this field (company).

I am assuming I need to override the registrations controller, or is there a better/easier way I should be approaching this?

Override devise registrations controller

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我已经在注册表单中添加了一个基于不同模型的字段，详细信息请参见。这部分运行得很好。现在的问题是，当我保存时，注册控制器的创建操作失败，注册控制器是由devise提供的，在这个字段(公司)上有一个Activerecord::UnknownAttributeError。我假设我需要覆盖注册控制器，或者有没有更好/更简单的方...

问覆盖设备注册控制器
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问覆盖设备注册控制器EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问覆盖设备注册控制器
EN