Note that there are some explanatory texts on larger screens.

plurals
  1. POWebbrick won't include the correct .css file
    primarykey
    data
    text
    <p>I'm following one of the best tutorials/books I have ever come across, the <a href="http://ruby.railstutorial.org/chapters/rails-flavored-ruby#sec%3acascading_style_sheets" rel="nofollow">Ruby On Rails Tutorial</a> but I am trying to include the "blueprint" stylesheets and assets/blueprint/screen.css returns this:</p> <pre><code>&lt;html lang="en"&gt; &lt;head&gt; &lt;meta charset="utf-8" /&gt; &lt;title&gt;Action Controller: Exception caught&lt;/title&gt; </code></pre> <p>I have checked that the path to the file is correct: C:\triton2\public\stylesheets\blueprint\screen.css</p> <p>And this is the top of my application.html.erb:</p> <pre><code> &lt;!DOCTYPE html&gt; &lt;html&gt; &lt;head&gt; &lt;title&gt;&lt;%= title %&gt;&lt;/title&gt; &lt;%= csrf_meta_tag %&gt; &lt;%= stylesheet_link_tag 'blueprint/screen.css', :media =&gt; 'screen' %&gt; &lt;%= stylesheet_link_tag 'blueprint/print.css', :media =&gt; 'print' %&gt; &lt;/head&gt; </code></pre> <p>Any idea what could be causing this? Better yet, how could I diagnose the proper solution on my own? Nothing on the google is of use save <a href="http://old.nabble.com/Re%3A-Action-Controller%3A-Exception-caught-p32852379.html" rel="nofollow">this which recommended a db:migrate</a> (didn't help)</p> <p>[edit] The solution was to put the style sheet in C:\triton2\public\assets\stylesheets\blueprint\screen.css and change application.html.erb to &lt;%= stylesheet_link_tag 'stylesheets/blueprint/print.css', :media => 'print' %></p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload