blocks|key|3223733|text|def+create+
+@material+=+Material.new(params[:material])
+@material.user_id+=+current_user.id+if+current_user
+if+@material.save
++flash[:success]+=+"Content+Successfully+Created"
++redirect_to+@material
+else
++render+'new'
+end
end|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|3223734|unstyled|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$B|C]]|$1|D|3|-4|5|E|7|H|8|@]|9|@]|A|$]]]|F|$]]

<pre><code>def create 
 @material = Material.new(params[:material])
 @material.user_id = current_user.id if current_user
 if @material.save
 flash[:success] = "Content Successfully Created"
 redirect_to @material
 else
 render 'new'
 end
end
</code></pre>

blocks|key|2742348|text|有几种不同的方法可以做到这一点，这取决于您如何设置您的应用程序。如果用户和材质之间存在关系(用户有许多材质)，则可以在控制器中使用该关系：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2742349|def+create
++@material+=+current_user.materials.new(params[:material])
++#+...
end|code-block|syntax|javascript|2742350|如果您没有这种关系，我仍然建议您在控制器中设置它，而不是在表单中设置隐藏字段。这将更加安全，因为它不会让人篡改用户id值：|2742351|def+create
++@material+=+Material.new(params[:material].merge(user_id:+current_user))
++#+...
end|2742352|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

There are a few different ways to do it depending on how you have your application setup. If there is a relationship between the user and materials (User has many materials), you could use that in your controller:

<pre><code>def create
 @material = current_user.materials.new(params[:material])
 # ...
end
</code></pre>

If you don't have that relationship, I would still recommend setting it in the controller as opposed to a hidden field in the form. This will be more secure because it won't let someone tamper with the user id value:

<pre><code>def create
 @material = Material.new(params[:material].merge(user_id: current_user))
 # ...
end
</code></pre>

blocks|key|2742307|text|假设您正在将登录用户的对象保存在current_user中，则可以使用以下命令|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2742308|+++@material+=+Material.new(params[:material])
+++@material.user_id+=+current_user.id
+++if+@material.save|code-block|syntax|javascript|2742309|entityMap^0|G|C|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|P|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|L|$]]

Assuming you are saving the login users's object in the <code>current_user</code> following will work for you

<pre><code> @material = Material.new(params[:material])
 @material.user_id = current_user.id
 if @material.save
</code></pre>

blocks|key|4952981|text|在创建对象之前，对于Rails5和需要对参数进行permit的参数，这是将current_user合并到参数中的最简单的方法，@Peter+Brown在他的回答中表示赞许：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4952982|def+create
++@discussion+=+current_user.materials.new(new_material_params)
++#+...
end

private
def+new_material_params
++params.require(:material).permit(:title,+:description,:+content)
end|code-block|syntax|javascript|4952983|如果您使用accepts_nested_attributes_for创建嵌套对象，则需要手动合并到关联参数中：|4952984|class+User+<+ApplicationRecord
++has_many+:discussions+#+Used+to+associate+User+with+Discussion+later
end

class+Comment+<+ApplicationRecord
++belongs_to+:user
end

class+Discussion+<+ApplicationRecord
++belongs_to+:user
++has_many+:comments
++accepts_nested_attributes_for+:comments
end

class+DiscussionsController+<+ApplicationController
++def+create
++++#+Merge+the+params[:discussion][:user_id]+by+using+the+relationship's+#new
++++@discussion+=+current_user.discussion.new(new_discussion_params)
++end

++private
++#+Sanitized+params+for+creation,+not+editing
++def+new_discussion_params
++++params.require(:discussion)
++++++.permit(:title,+:user_id,+
++++++++++++++comments_attributes:+[:id,+:content,+:discussion_id,+:user_id])
++++++.tap+do+%7Cdiscussion_params%7C
++++++++#+Require+the+association+parameters,+and+if+they+exist,
++++++++#+set+:user_id+for+each.
++++++++discussion_params.require(:comments_attributes).each+do+%7Ci,+comment%7C
++++++++++comment.merge!(user_id:+current_user.id)
++++++++end
++++end
++end
end|4952985|Heads：设置(或覆盖！)什么将是params[:discussion][:comments_attributes]["0"][:user_id]在创建时运行良好。但是，如果您允许除了创建之外还编辑深层层次结构，请确保您不会意外地用当前用户覆盖所有的:user_id。|BOLD|4952986|entityMap^0|O|6|11|C|0|0|5|T|0|0|0|6|I|1K|3I|8|0^^$0|@$1|2|3|4|5|6|7|T|8|@$9|U|A|V|B|C]|$9|W|A|X|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|Y|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|Z|8|@$9|10|A|11|B|C]]|D|@]|E|$]]|$1|M|3|N|5|H|7|12|8|@]|D|@]|E|$I|J]]|$1|O|3|P|5|6|7|13|8|@$9|14|A|15|B|Q]|$9|16|A|17|B|C]|$9|18|A|19|B|C]]|D|@]|E|$]]|$1|R|3|-4|5|6|7|1A|8|@]|D|@]|E|$]]]|S|$]]

With Rails 5 and parameters needing to be <code>permit</code>ted before objects are created, this is the simplest way to merge the <code>current_user</code> into the params, kudos to @Peter Brown in his answer:

<pre><code>def create
 @discussion = current_user.materials.new(new_material_params)
 # ...
end

private
def new_material_params
 params.require(:material).permit(:title, :description,: content)
end
</code></pre>

If you have nested object creation using <code>accepts_nested_attributes_for</code>, you need to manually merge deep into the association parameters:

<pre><code>class User &lt; ApplicationRecord
 has_many :discussions # Used to associate User with Discussion later
end

class Comment &lt; ApplicationRecord
 belongs_to :user
end

class Discussion &lt; ApplicationRecord
 belongs_to :user
 has_many :comments
 accepts_nested_attributes_for :comments
end

class DiscussionsController &lt; ApplicationController
 def create
 # Merge the params[:discussion][:user_id] by using the relationship's #new
 @discussion = current_user.discussion.new(new_discussion_params)
 end

 private
 # Sanitized params for creation, not editing
 def new_discussion_params
 params.require(:discussion)
 .permit(:title, :user_id, 
 comments_attributes: [:id, :content, :discussion_id, :user_id])
 .tap do |discussion_params|
 # Require the association parameters, and if they exist,
 # set :user_id for each.
 discussion_params.require(:comments_attributes).each do |i, comment|
 comment.merge!(user_id: current_user.id)
 end
 end
 end
end
</code></pre>

Heads up: Setting (or overwriting!) what will be <code>params[:discussion][:comments_attributes]["0"][:user_id]</code> works fine for creation. But if you allow editing deep hierarchies in addition to creation, make sure you don't accidentally overwrite all the <code>:user_id</code>s with the current user.

I have a form for creating materials (title, description and content - all basic). The form saves these details just fine but it doesn't save the user_id, which should be the user_id of the current_user. How do I do this? It must be easy but nothing has worked so far.

<pre><code>def create 
 @material = Material.new(params[:material])
 if @material.save
 flash[:success] = "Content Successfully Created"
 redirect_to @material
 else
 render 'new'
 end
end
</code></pre>

How to add current_user to user_id to form_for in rails?

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

我有一个创建材料的表单(标题，描述和内容-都是基本的)。表单可以很好地保存这些详细信息，但不会保存user_id，它应该是current_user的user_id。我该怎么做呢？这肯定很简单，但到目前为止还没有任何工作。def create    @material = Material.new(params[:material])   if @material.save     flash[:s

问如何在rails中添加current_user to user_id to form_for？
EN

回答 4

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在rails中添加current_user to user_id to form_for？EN

回答 4

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在rails中添加current_user to user_id to form_for？
EN