Sha256: a058f518d2797e606622d75e9331b719c11edf1486bd19f3b90feb4ce4cef63c
Contents?: true
Size: 1.26 KB
Versions: 12
Compression:
Stored size: 1.26 KB
Contents
<header role="banner">
<h1>No view template for interactive request</h1>
</header>
<main id="container">
<h2><%= h @exception.message %></h2>
<div class="summary">
<p>
<strong>NOTE:</strong> Rails usually expects a controller action to render a view template with the same name.
</p>
<p>
For example, a <code><%= @exception.controller %>#<%= @exception.action_name %></code> action defined in <code>app/controllers/<%= @exception.controller.controller_path %>_controller.rb</code> should have a corresponding view template
in a file named <code>app/views/<%= @exception.controller.controller_name %>/<%= @exception.action_name %>.html.erb</code>.
</p>
<p>
However, if this controller is an API endpoint responding with 204 (No Content), which does not require a view template because it doesn't serve an HTML response, then this error will occur when trying to access it with a browser. In this particular scenario, you can ignore this error.
</p>
<p>
You can find more about view template rendering conventions in the <a href="https://guides.rubyonrails.org/layouts_and_rendering.html#rendering-by-default-convention-over-configuration-in-action">Rails Guides on Layouts and Rendering in Rails</a>.
</p>
</div>
</main>
Version data entries
12 entries across 12 versions & 3 rubygems