blocks|key|2310416|text|路线上有个错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2310417|/积/索引=>+product#index|2310418|/admin/product/index+=>+product#index|2310419|它们都指向与产品相同的contoller名称。|2310420|我建议这些路线|2310421|resources++:admin+do+
++resources+:product+do+
++end
end

resources+:product+do+
end|code-block|syntax|javascript|2310422|通过这样做，可以确保您有两个产品控制器。一个带有Admin::ProductController第二个ProductController|2310423|admin_product_path用于管理视图，product_path用于普通视图|2310424|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|6|7|X|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|Y|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|Z|8|@]|9|@]|A|$M|N]]|$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|$]]

There is a Mistake in routes .

/product/index => product#index

/admin/product/index => product#index

Both pointing to the same contoller names as product.

I would suggest these routes

<pre><code>resources :admin do 
 resources :product do 
 end
end

resources :product do 
end
</code></pre>

By doing so you make sure that you have two products Controller.
 One with Admin::ProductController
Second ProductController

admin_product_path for admin view
product_path for normal view

blocks|key|1075423|text|在您的控制器中，只需呈现您想为用户服务的视图，我的意思是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1075424|ProductsController
def+index
++#+...
++render+'index'
end

Admin::ProductsController
def+index
++#+...
++render+'products/index'
end|code-block|syntax|javascript|1075425|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

From within your controllers, just render view you want to serve for user, I mean:

<pre><code>ProductsController
def index
 # ...
 render 'index'
end

Admin::ProductsController
def index
 # ...
 render 'products/index'
end
</code></pre>

blocks|key|1075496|text|在使用Rails+6应用程序时，我遇到了这个挑战。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1075497|我有两种类型的用户：Customers和Admins。我使用设计+gem进行身份验证。我希望产品视图的Customer与Admins视图不同。|1075498|我已经在控制器中有了一个目录--为Admins设计配置。|1075499|，这是我怎么做的，|1075500|首先，使用命名空间为Admins+products视图定义一个新的products路由admins。|CODE|1075501|namespace+:admins+do
++resources+:products+do
++end
end|code-block|syntax|javascript|1075502|注意事项：这将影响管理员的路径/URL。比方说，products_path不会是admins_products_path。|1075503|然后，在控制器中将products_controller.rb添加到app/controllers/admins目录中：|1075504|class+Admins::ProductsController+<+ApplicationController
++before_action+:set_product,+only:+[:show,+:edit,+:update,+:destroy]

++#+GET+/products
++#+GET+/products.json
++def+index
++++@products+=+Product.all
++end

++#+GET+/products/1
++#+GET+/products/1.json
++def+show
++end

++#+GET+/products/new
++def+new
++++@product+=+Product.new
++end

++#+GET+/products/1/edit
++def+edit
++end

++#+POST+/products
++#+POST+/products.json
++def+create
++++@product+=+Product.new(product_params)

++++respond_to+do+%7Cformat%7C
++++++if+@product.save
++++++++format.html+{+redirect_to+admins_product_path(@product),+notice:+'Product+was+successfully+created.'+}
++++++++format.json+{+render+:show,+status:+:created,+location:+admins_product_path(@product)+}
++++++else
++++++++format.html+{+render+:new+}
++++++++format.json+{+render+json:+@product.errors,+status:+:unprocessable_entity+}
++++++end
++++end
++end

++#+PATCH/PUT+/products/1
++#+PATCH/PUT+/products/1.json
++def+update
++++respond_to+do+%7Cformat%7C
++++++if+@product.update(product_params)
++++++++format.html+{+redirect_to+admins_product_path(@product),+notice:+'Product+was+successfully+updated.'+}
++++++++format.json+{+render+:show,+status:+:ok,+location:+admins_product_path(@product)+}
++++++else
++++++++format.html+{+render+:edit+}
++++++++format.json+{+render+json:+@product.errors,+status:+:unprocessable_entity+}
++++++end
++++end
++end

++#+DELETE+/products/1
++#+DELETE+/products/1.json
++def+destroy
++++@product.destroy
++++respond_to+do+%7Cformat%7C
++++++format.html+{+redirect_to+admins_products_url,+notice:+'Product+was+successfully+destroyed.'+}
++++++format.json+{+head+:no_content+}
++++end
++end

++private
++++#+Use+callbacks+to+share+common+setup+or+constraints+between+actions.
++++def+set_product
++++++@product+=+Product.find(params[:id])
++++end

++++#+Only+allow+a+list+of+trusted+parameters+through.
++++def+product_params
++++++params.require(:product).permit(:name,+:sku,+:short_description,+:full_description)
++++end
end|1075505|注意事项：注意使用Admins模块的ProductsController名称空间以及create、update和destroy操作中的修改路径|1075506|最后，在视图中，在app/views/admins/products目录中添加与Admins产品关联的视图。|1075507|注意事项：您可能必须修改视图中的路径，以便与管理员产品的路由相对应。比如说，admins+products的视图将是admins_product_path(product)，而不是product或product_path(product)。|1075508|有一种使用单元格+gem的更干净的方法。这消除了重复代码的需要，而且当您需要为最多3个或更多角色定义视图时，它也会派上用场。您可以在这里阅读更多关于如何使用它的内容：Rails中的面向对象视图。|1075509|就这样。|1075510|我希望这对有帮助|1075511|entityMap|0|LINK|mutability|MUTABLE|url|https://trailblazer.to/2.0/gems/cells/|1|https://datarockets.com/blog/object-oriented-views-in-rails/^0|3|7|0|A|9|K|6|U|2|1A|2|1F|8|1O|6|0|4|3|C|D|0|0|9|0|5|19|H|8|X|8|17|6|0|0|0|1P|O|D|14|K|0|0|1O|9|M|Y|M|0|0|0|1Z|16|6|1D|6|1K|7|0|0|1I|9|P|0|0|3C|1M|S|2I|7|2Q|L|0|0|2P|5|3|0|2B|D|1|0|0|4|0|0|8|0^^$0|@$1|2|3|4|5|6|7|1L|8|@$9|1M|A|1N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1O|8|@$9|1P|A|1Q|B|C]|$9|1R|A|1S|B|C]|$9|1T|A|1U|B|C]|$9|1V|A|1W|B|C]|$9|1X|A|1Y|B|C]|$9|1Z|A|20|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|21|8|@$9|22|A|23|B|C]|$9|24|A|25|B|C]]|D|@]|E|$]]|$1|J|3|K|5|6|7|26|8|@$9|27|A|28|B|C]]|D|@]|E|$]]|$1|L|3|M|5|6|7|29|8|@$9|2A|A|2B|B|C]|$9|2C|A|2D|B|N]|$9|2E|A|2F|B|N]|$9|2G|A|2H|B|N]]|D|@]|E|$]]|$1|O|3|P|5|Q|7|2I|8|@]|D|@]|E|$R|S]]|$1|T|3|U|5|6|7|2J|8|@$9|2K|A|2L|B|C]|$9|2M|A|2N|B|N]|$9|2O|A|2P|B|N]]|D|@]|E|$]]|$1|V|3|W|5|6|7|2Q|8|@$9|2R|A|2S|B|C]|$9|2T|A|2U|B|N]|$9|2V|A|2W|B|N]]|D|@]|E|$]]|$1|X|3|Y|5|Q|7|2X|8|@]|D|@]|E|$R|S]]|$1|Z|3|10|5|6|7|2Y|8|@$9|2Z|A|30|B|C]|$9|31|A|32|B|N]|$9|33|A|34|B|N]|$9|35|A|36|B|N]]|D|@]|E|$]]|$1|11|3|12|5|6|7|37|8|@$9|38|A|39|B|C]|$9|3A|A|3B|B|N]]|D|@]|E|$]]|$1|13|3|14|5|6|7|3C|8|@$9|3D|A|3E|B|C]|$9|3F|A|3G|B|N]|$9|3H|A|3I|B|N]|$9|3J|A|3K|B|N]]|D|@]|E|$]]|$1|15|3|16|5|6|7|3L|8|@$9|3M|A|3N|B|C]]|D|@$9|3O|A|3P|1|3Q]|$9|3R|A|3S|1|3T]]|E|$]]|$1|17|3|18|5|6|7|3U|8|@$9|3V|A|3W|B|C]]|D|@]|E|$]]|$1|19|3|1A|5|6|7|3X|8|@$9|3Y|A|3Z|B|C]]|D|@]|E|$]]|$1|1B|3|-4|5|6|7|40|8|@]|D|@]|E|$]]]|1C|$1D|$5|1E|1F|1G|E|$1H|1I]]|1J|$5|1E|1F|1G|E|$1H|1K]]]]

I faced this challenge when working on a Rails 6 application.
I had two types of users: Customers and Admins. I was using the Devise gem for authentication. I wanted the Products views for the Customer to be different from the Admins View.
I already had an <code>app/controllers/admins</code> directory in the controllers for the Devise configuration for Admins.
Here's how I did it:
First, define a new route for the Admins <code>products</code> view using the <code>admins</code> namespace.
<pre><code>namespace :admins do
 resources :products do
 end
end
</code></pre>
Note: This will affect the Paths/URLs for the Admins. Say, the <code>products_path</code> will not be <code>admins_products_path</code>.
Then, in the controllers add the <code>products_controller.rb</code> to the <code>app/controllers/admins</code> directory:
<pre><code>class Admins::ProductsController &lt; ApplicationController
 before_action :set_product, only: [:show, :edit, :update, :destroy]

 # GET /products
 # GET /products.json
 def index
 @products = Product.all
 end

 # GET /products/1
 # GET /products/1.json
 def show
 end

 # GET /products/new
 def new
 @product = Product.new
 end

 # GET /products/1/edit
 def edit
 end

 # POST /products
 # POST /products.json
 def create
 @product = Product.new(product_params)

 respond_to do |format|
 if @product.save
 format.html { redirect_to admins_product_path(@product), notice: 'Product was successfully created.' }
 format.json { render :show, status: :created, location: admins_product_path(@product) }
 else
 format.html { render :new }
 format.json { render json: @product.errors, status: :unprocessable_entity }
 end
 end
 end

 # PATCH/PUT /products/1
 # PATCH/PUT /products/1.json
 def update
 respond_to do |format|
 if @product.update(product_params)
 format.html { redirect_to admins_product_path(@product), notice: 'Product was successfully updated.' }
 format.json { render :show, status: :ok, location: admins_product_path(@product) }
 else
 format.html { render :edit }
 format.json { render json: @product.errors, status: :unprocessable_entity }
 end
 end
 end

 # DELETE /products/1
 # DELETE /products/1.json
 def destroy
 @product.destroy
 respond_to do |format|
 format.html { redirect_to admins_products_url, notice: 'Product was successfully destroyed.' }
 format.json { head :no_content }
 end
 end

 private
 # Use callbacks to share common setup or constraints between actions.
 def set_product
 @product = Product.find(params[:id])
 end

 # Only allow a list of trusted parameters through.
 def product_params
 params.require(:product).permit(:name, :sku, :short_description, :full_description)
 end
end
</code></pre>
Note: Take note of the ProductsController namespacing using the Admins Module and the modified paths in the <code>create</code>, <code>update</code> and <code>destroy</code> actions od the
And finally, in the views, add the views associated with the Admins Products in the <code>app/views/admins/products</code> directory.
Note: You may have to modify the paths in the views to correspond with the routes for the admins products. Say, the <code>show</code> view for admins products will be <code>admins_product_path(product)</code> and not <code>product</code> or <code>product_path(product)</code>.
There is a cleaner approach using the <a href="https://trailblazer.to/2.0/gems/cells/" rel="nofollow noreferrer">cells</a> gem. This eliminates the need to duplicate code, and it comes in handy when you need to define views for up to 3 or more roles. You can read up more about how to use it here: <a href="https://datarockets.com/blog/object-oriented-views-in-rails/" rel="nofollow noreferrer">Object-Oriented Views in Rails</a>.
That's all.
I hope this helps

I have 2 versions of an same index page which display a list of products.
Regular view - Displays List
Admin view - Displays List with options to edit, delete etc.

The index action just makes the database query and returns that instance variable.
Currently, I have the same index action for rendering the index page. I want to reuse the index action form product into the admin controller.

<pre><code>def index
 @products = Product.all
end
</code></pre>

routes:

<pre><code>/product/index =&gt; product#index

/admin/product/index =&gt; product#index
</code></pre>

I tried the prepend_view_path technique given [here | <a href="https://stackoverflow.com/questions/6055319/how-can-i-intercept-railss-template-rendering]">How can I intercept rails&#39;s template rendering</a>, but then this always ends up rendering the admin/product/index.html.erb file in both cases.

I want the Product#index controller#action to render:

<blockquote>
 /index.html.erb for /product/index
</blockquote>

and 

<blockquote>
 /admin/product/index.html.erb for /admin/product/index
</blockquote>

Can someone help me with how this could be done in an elegant way instead of just writing the same action for admin controller class and product controller class.

PS: I'm just one week into ruby and ruby on rails. Any help is much appreciated.

Rails - Multiple Views(admin, regular) from same action(index)

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

我有两个版本的同一索引页，显示产品列表。常规视图-显示列表管理视图-显示具有编辑、删除等选项的列表。index操作只是进行数据库查询并返回该实例变量。当前，我有相同的索引操作来呈现索引页面。我希望将索引操作表单产品重用到管理控制器中。def index    @products = Product.allend路线：/...

问Rails -来自相同操作(索引)的多个视图(管理，常规)
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Rails -来自相同操作(索引)的多个视图(管理，常规)EN