blocks|key|1499732|text|Rails具有基本的CRUD默认操作。此外，根据HTTP谓词，每个动作都可以有不同的处理。还可以添加自定义操作和路由。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1499733|对于每个默认操作，最好遵循标准的Rails实践。例如，“新”操作应该路由到表单，以便在通过GET访问时创建一个新用户。HTTP到表单应该路由到"create“操作。|1499734|如果需要添加额外的控制器操作，请使用自定义方法。我再次强调，简单的CRUD操作应该遵循正常的Rails约定。|1499735|阅读更多关于路由的信息|offset|length|1499736|要理解Rails中的简单CRUD操作，请多次阅读本指南|1499737|entityMap|0|LINK|mutability|MUTABLE|url|http://guides.rubyonrails.org/routing.html|1|http://guides.rubyonrails.org/getting_started.html^0|0|0|0|6|2|0|0|3|F|1|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|X|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Y|8|@]|9|@$H|Z|I|10|1|11]]|A|$]]|$1|J|3|K|5|6|7|12|8|@]|9|@$H|13|I|14|1|15]]|A|$]]|$1|L|3|-4|5|6|7|16|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S]]|T|$5|O|P|Q|A|$R|U]]]]

Rails has basic CRUD default actions. Additionally each action can have different processing depending on the HTTP verb. You can also add custom actions &amp; routes.

It is best to follow standard Rails practices for each default action. For example, "new" action should route to the form to create a new user when accessed via GET. An HTTP POST to the form should route to the "create" action. 

If you need to add an additional controller action, do so with a custom method. Again, I stress, simple CRUD actions should follow normal Rails conventions. 

Read more about <a href="http://guides.rubyonrails.org/routing.html" rel="nofollow">routing</a> 
Read this guide many times to understand <a href="http://guides.rubyonrails.org/getting_started.html" rel="nofollow">simple CRUD actions in Rails</a>

blocks|key|333374|text|默认情况下，Rails将查找与控制器同名的布局，否则将查找application.html.erb。但您也可以指定一个控制器范围(这对您没有帮助，但请容忍我)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|333375|class+SomethingController
++layout+"some_name"
++...|code-block|syntax|javascript|333376|这仍然是布局范围，所以不是你所需要的。|333377|但是，您也可以在操作中为每个对render的调用指定特定的布局：|offset|length|style|CODE|333378|def+edit
+++#some+logic
+++render+"some_template",+:layout+=>+"some_layout"
end|333379|或者，接受默认的模板查找，但仍然指定布局：|333380|def+edit
+++#+some+logic
+++render+:layout+=>+"some_layout"
end|333381|还有一种方法可以指定布局，这可能特别适合于“一个布局(如果没有登录，另一个布局是登录的话)”的用例：|333382|class+SomeController
+++layout+:method_name_to_determine_layout

+++#+...+actions+...

+++protected
+++def+method_name_to_determine_layout
+++++if+current_user
++++++++"logged_in_layout_name"
+++++else
++++++++"not_logged_in_layout_name"
+++++end
+++end|333383|您可以了解更多关于在布局和渲染Rails指南中指定布局的不同方法的信息。|333384|希望这能有所帮助。|333385|entityMap|0|LINK|mutability|MUTABLE|url|http://guides.rubyonrails.org/layouts_and_rendering.html^0|0|0|0|F|6|0|0|0|0|0|0|A|C|0|0|0^^$0|@$1|2|3|4|5|6|7|1A|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|1B|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|1C|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|1D|8|@$K|1E|L|1F|M|N]]|9|@]|A|$]]|$1|O|3|P|5|D|7|1G|8|@]|9|@]|A|$E|F]]|$1|Q|3|R|5|6|7|1H|8|@]|9|@]|A|$]]|$1|S|3|T|5|D|7|1I|8|@]|9|@]|A|$E|F]]|$1|U|3|V|5|6|7|1J|8|@]|9|@]|A|$]]|$1|W|3|X|5|D|7|1K|8|@]|9|@]|A|$E|F]]|$1|Y|3|Z|5|6|7|1L|8|@]|9|@$K|1M|L|1N|1|1O]]|A|$]]|$1|10|3|11|5|6|7|1P|8|@]|9|@]|A|$]]|$1|12|3|-4|5|6|7|1Q|8|@]|9|@]|A|$]]]|13|$14|$5|15|16|17|A|$18|19]]]]

By default, Rails will look-up a layout with the same name as the controller, or else application.html.erb. But you can also specify one controller-wide (which won't help you, but bear with me)

<pre><code>class SomethingController
 layout "some_name"
 ...
</code></pre>

That's still layout-wide, so not what you need. 

But you can also specify a specific layout on each call to <code>render</code> in an action:

<pre><code>def edit
 #some logic
 render "some_template", :layout =&gt; "some_layout"
end
</code></pre>

Or, to take the default template lookup, but still specify a layout:

<pre><code>def edit
 # some logic
 render :layout =&gt; "some_layout"
end
</code></pre>

There's another way you can specify layouts too, which might be especially appropriate for the use case of "one layout if not logged in, another if logged in":

<pre><code>class SomeController
 layout :method_name_to_determine_layout

 # ... actions ...

 protected
 def method_name_to_determine_layout
 if current_user
 "logged_in_layout_name"
 else
 "not_logged_in_layout_name"
 end
 end
</code></pre>

You can learn more about the different ways to specify layouts in the <a href="http://guides.rubyonrails.org/layouts_and_rendering.html" rel="nofollow">Layouts and Rendering Rails Guide</a>

Hope this helps.

blocks|key|948509|text|我决定使用单独的控制器，而不是在两个布局中使用1个控制器。因此，我有profile_controller，它有“编辑”和“更新”帐户设置和“显示”显示配置文件。我也是users_controller，它有以下内容:登录、login_attempt、注册、signup_attempt等等。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|948510|所以，我不是把注册和编辑在一个控制器，而是使用两个不同的控制器是更好和干净，我想。|948511|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Instead of using 1 controller in 2 layouts, I decided to use separate controllers. So, I have profile_controller, which has "edit" and "update" for account settings and "show" to display profile. And I also users_controller, which has followings: login, login_attempt, signup, signup_attempt, etc.. 

So, I am not putting signup and edit together in 1 controller, instead using 2 different controllers is much better and clean, I guess.

blocks|key|1499996|text|听起来你在尝试自己的身份验证。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1499997|我建议使用Devise.+这里的教程很棒|offset|length|style|CODE|1499998|​|1499999|📷|atomic|1500000|1500001|原因有两方面。|1500002|首先，使您能够将应用程序划分为通过身份验证的用户和非身份验证的用户。也就是说，它提供user_signed_in?、devise_controller?和current_user帮助来帮助这一点。|1500003|这看起来可能不是什么大问题，但它实际上会帮助您完成布局(稍后我会描述更多)。|1500004|其次是，设计是预轧制的.您有关如何处理signups和registrations的问题已经解决了。当然，没有什么可以阻止您进行自己的身份验证(Devise毕竟是建立在Warden上的)，但是它应该给您一些已经完成的方法的一些想法。|BOLD|1500005|对于您最初的问题(关于布局)，另一个答案非常好(在设置每个方法的layouts等方面)。|1500006|此外，我要说的是，您必须记住Rails是一系列类。因此，在layout中设置controller选项是确保得到正确选项的最佳方法。|1500007|这是Rails对它的解释|1500008|#app/controllers/application_controller.rb
class+ApplicationController+<+ActionController::Base
+++layout+:your_layout

+++private

+++def+your_layout
++++++devise_controller?+%7C%7C+!user_signed_in?+?+"new_user"+:+"application"
+++end
end|code-block|syntax|javascript|1500009|我发现最好保持你的逻辑尽可能简洁。该布局只有一套逻辑。我们倾向于将其保存在ApplicationController中，必要时将其覆盖。|1500010|--|1500011|最后，您的问题还突出了对Rails的基本误解。我不是不尊重你；我发现你对框架的看法越清晰，你就越能更好地处理它：|1500012|1500013|1500014|1500015|您必须记住Rails的几个要点：|1500016|这是一个MVC+(Model+V+Controller)框架|ordered-list-item|1500017|它建立在Ruby之上，因此是面向对象的|1500018|也许我应该把“新”和“创建”放在一个注册控制器中。这是我困惑的地方。|blockquote|1500019|如果您将Devise作为模型，您将看到可以将控制器视为对象的抽象层。也就是说，正如Devise向我们展示的那样，您可以拥有sessions和registrations控制器。|1500020|我并不提倡你这样做，我只是想表明，如果你把注意力放在你正在处理的对象上，你的控制器操作应该放在哪里就变得更清楚了。|1500021|您也将最好地理解CRUD+(Create+Read+Update+D雌激素)+Rails控制器和对象的性质。标准Rails控制器是这样设置的：|1500022|1500023|1500024|1500025|虽然这并不严格，但它确实给了您另一个指示，说明您的控制器应该遵循的结构。|1500026|你可能已经知道这事了！|1500027|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/plataformatec/devise|1|http://railscasts.com/episodes/209-introducing-devise|2|IMAGE|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/f82d5175b58c9a655e9781654ed0cc6c.png|imageAlt|3|https://github.com/plataformatec/devise#controller-filters-and-helpers|4|http://www.rubydoc.info/github/plataformatec/devise/Devise/Controllers/Helpers#devise_controller%253F-instance_method|5|6|http://api.rubyonrails.org/classes/ActionView/Layouts.html|7|https://developer.qcloudimg.com/http-save/yehe-900000/a387ad7b880281399f3ca97b74adfce2.png|8|https://developer.qcloudimg.com/http-save/yehe-900000/6bcb38357ad662f100d9beaf4b7f0ae9.png^0|0|5|6|5|6|0|D|7|1|0|0|0|1|2|0|0|0|16|F|1M|I|25|C|16|F|3|1M|I|4|25|C|5|0|0|0|3|J|7|R|D|2B|6|0|W|7|0|T|6|12|A|0|2|A|6|0|0|11|L|0|0|0|0|0|1|7|0|0|0|9|1|F|1|H|1|0|0|0|4|6|1P|8|1Y|D|0|0|E|1|L|1|Q|1|X|1|0|0|0|1|8|0|0|0|0^^$0|@$1|2|3|4|5|6|7|2U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|2V|8|@$D|2W|E|2X|F|G]]|9|@$D|2Y|E|2Z|1|30]|$D|31|E|32|1|33]]|A|$]]|$1|H|3|I|5|6|7|34|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|35|8|@]|9|@$D|36|E|37|1|38]]|A|$]]|$1|M|3|I|5|6|7|39|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|3A|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|3B|8|@$D|3C|E|3D|F|G]|$D|3E|E|3F|F|G]|$D|3G|E|3H|F|G]]|9|@$D|3I|E|3J|1|3K]|$D|3L|E|3M|1|3N]|$D|3O|E|3P|1|3Q]]|A|$]]|$1|R|3|S|5|6|7|3R|8|@]|9|@]|A|$]]|$1|T|3|U|5|6|7|3S|8|@$D|3T|E|3U|F|V]|$D|3V|E|3W|F|G]|$D|3X|E|3Y|F|G]|$D|3Z|E|40|F|G]]|9|@]|A|$]]|$1|W|3|X|5|6|7|41|8|@$D|42|E|43|F|G]]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|44|8|@$D|45|E|46|F|G]|$D|47|E|48|F|G]]|9|@]|A|$]]|$1|10|3|11|5|6|7|49|8|@]|9|@$D|4A|E|4B|1|4C]]|A|$]]|$1|12|3|13|5|14|7|4D|8|@]|9|@]|A|$15|16]]|$1|17|3|18|5|6|7|4E|8|@$D|4F|E|4G|F|G]]|9|@]|A|$]]|$1|19|3|1A|5|6|7|4H|8|@]|9|@]|A|$]]|$1|1B|3|1C|5|6|7|4I|8|@]|9|@]|A|$]]|$1|1D|3|I|5|6|7|4J|8|@]|9|@]|A|$]]|$1|1E|3|K|5|L|7|4K|8|@]|9|@$D|4L|E|4M|1|4N]]|A|$]]|$1|1F|3|I|5|6|7|4O|8|@]|9|@]|A|$]]|$1|1G|3|1H|5|6|7|4P|8|@]|9|@]|A|$]]|$1|1I|3|1J|5|1K|7|4Q|8|@$D|4R|E|4S|F|V]|$D|4T|E|4U|F|V]|$D|4V|E|4W|F|V]]|9|@]|A|$]]|$1|1L|3|1M|5|1K|7|4X|8|@]|9|@]|A|$]]|$1|1N|3|1O|5|1P|7|4Y|8|@]|9|@]|A|$]]|$1|1Q|3|1R|5|6|7|4Z|8|@$D|50|E|51|F|G]|$D|52|E|53|F|G]|$D|54|E|55|F|G]]|9|@]|A|$]]|$1|1S|3|1T|5|6|7|56|8|@]|9|@]|A|$]]|$1|1U|3|1V|5|6|7|57|8|@$D|58|E|59|F|V]|$D|5A|E|5B|F|V]|$D|5C|E|5D|F|V]|$D|5E|E|5F|F|V]]|9|@]|A|$]]|$1|1W|3|I|5|6|7|5G|8|@]|9|@]|A|$]]|$1|1X|3|K|5|L|7|5H|8|@]|9|@$D|5I|E|5J|1|5K]]|A|$]]|$1|1Y|3|I|5|6|7|5L|8|@]|9|@]|A|$]]|$1|1Z|3|20|5|6|7|5M|8|@]|9|@]|A|$]]|$1|21|3|22|5|6|7|5N|8|@]|9|@]|A|$]]|$1|23|3|-4|5|6|7|5O|8|@]|9|@]|A|$]]]|24|$25|$5|26|27|28|A|$29|2A]]|2B|$5|26|27|28|A|$29|2C]]|2D|$5|2E|27|2F|A|$2G|2H|2I|-4]]|2J|$5|26|27|28|A|$29|2K]]|2L|$5|26|27|28|A|$29|2M]]|2N|$5|26|27|28|A|$29|2K]]|2O|$5|26|27|28|A|$29|2P]]|2Q|$5|2E|27|2F|A|$2G|2R|2I|-4]]|2S|$5|2E|27|2F|A|$2G|2T|2I|-4]]]]

Sounds like you're trying to roll your own authentication.

I'd recommend using <a href="https://github.com/plataformatec/devise" rel="nofollow noreferrer"><code>Devise</code></a>... <a href="http://railscasts.com/episodes/209-introducing-devise" rel="nofollow noreferrer">great tutorial here</a>:

<a href="https://i.stack.imgur.com/mWcLV.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/mWcLV.png" alt="enter image description here"></a>

The reason for this is two-fold.

Firstly, Devise gives you the ability to split your app between authenticated and non-authenticated users. Namely, it provides the <a href="https://github.com/plataformatec/devise#controller-filters-and-helpers" rel="nofollow noreferrer"><code>user_signed_in?</code></a>, <a href="http://www.rubydoc.info/github/plataformatec/devise/Devise/Controllers/Helpers#devise_controller%3F-instance_method" rel="nofollow noreferrer"><code>devise_controller?</code></a> and <a href="https://github.com/plataformatec/devise#controller-filters-and-helpers" rel="nofollow noreferrer"><code>current_user</code></a> helpers to aid with this.

This might not appear like a big deal, but it will actually help you with your layouts (I'll describe more in a second).

Secondly, Devise is pre-rolled. Your questions about how to handle <code>signups</code> and <code>registrations</code> have already been solved. Of course, there's nothing preventing you from making your own authentication (Devise is just built on <code>Warden</code> after all), but it should give you some ideas on how this has been done already.

<hr>

In regards your original question (about layouts), the other answer is very good (in terms of setting <code>layouts</code> per method etc).

To add to it, I would say that you have to remember that Rails is a series of classes. As such, setting the <code>layout</code> option in the <code>controller</code> is the best way to ensure you're getting the correct one.

Here's <a href="http://api.rubyonrails.org/classes/ActionView/Layouts.html" rel="nofollow noreferrer">Rails explanation on it</a>:

<pre><code>#app/controllers/application_controller.rb
class ApplicationController &lt; ActionController::Base
 layout :your_layout

 private

 def your_layout
 devise_controller? || !user_signed_in? ? "new_user" : "application"
 end
end
</code></pre>

I've found it better to keep your logic as terse as possible. IE only have one set of logic for the layout. We tend to keep it in the <code>ApplicationController</code>, overriding where necessary.

--

Finally, your questions also highlighted a base misunderstanding of Rails. I'm not being disrespectful; I've found the clearer your perception of the framework, the better you can work with it:

<a href="https://i.stack.imgur.com/0h5Bi.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/0h5Bi.png" alt="enter image description here"></a>

You have to remember several key points with Rails:

<ol>
<li>It's an MVC (Model View Controller) framework</li>
<li>It's built on Ruby; hence is object orientated</li>
</ol>

<blockquote>
 maybe I should put "new" and "create" in a signup controller. This where I get confused.
</blockquote>

If you take <code>Devise</code> as a model, you'll see that you could treat your controllers as layers of abstraction for objects. That is, as Devise shows us, you can have <code>sessions</code> and <code>registrations</code> controllers.

I'm not advocating you do this exactly, I am trying to show that if you put the focus onto the objects you're working with, it becomes clearer where your controller actions should be placed.

You'll also be best understanding the CRUD (Create Read Update Destroy) nature of Rails controllers &amp; objects. The standard Rails controller is set up as such:

<a href="https://i.stack.imgur.com/VWzPH.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/VWzPH.png" alt="enter image description here"></a>

Whilst this is not strict, it does give you another indication as to the structure your controllers should adhere to. 

You may know this stuff already!

I have a logic question and I cannot figure out how to do it. First of all, I am working on an social networking site, and I completed the site in pure PHP, but now I am re-writing the backend in rails.

My questions is, I generated UsersController, it has new, create, show, edit, update, delete, and destroy.

I thought I could use "new" to display sign up page, "create" to process sign up, "show" to display profile page, "edit" to display account settings and "update" to process edit.

I might have a logic problem here, maybe I should put "new" and "create" in a signup controller. This where I get confused. The problem with the first logic I said, I have 2 layouts, one of them is for before login, and the other one is for after login. (You can imagine Facebook's header before login, and after login).

So, when I have 2 different layout, I cannot use 1 controller in 2 layout. Because sign up page has "before login header design" and account settings and profile has "after login header design". And as you can guess I define layout in controller.

I don't know if I explained well. Thank you.

Using 1 Controller in 2 layout

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

我有一个逻辑问题，我想不出怎么做。首先，我在一个社交网站上工作，我用纯PHP完成了这个网站，但现在我正在用rails重写后端。我的问题是，我生成了UsersController，它有新的、创建、显示、编辑、更新、删除和销毁。我想我可以使用“新”显示注册页面，“创建”处理注册，“显示”显示配置文件页面，“编辑”显示帐户设...

问在2个布局中使用1个控制器
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在2个布局中使用1个控制器EN