Databases
StackOverflow2013
Postsdbo
POCustom CSS via controller returning via #show/n?format=css but not #show/n.css
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POCustom CSS via controller returning via #show/n?format=css but not #show/n.css
    primarykey
    data
    text
    <p>I am implementing a custom theming issue for a Rails 3.2 app, with a very small number of CSS overrides for each theme.</p> <p>While I have so far implemented the theme variations by inlining some CSS (including occasional Erb parameters) within the layout file, I'd really like to tidy this up by delivering the customisation CSS via a GET request, e.g.: (assume <code>current_theme</code> is defined)</p> <pre><code>&lt;%= stylesheet_link_tag theme_path(current_theme, format: :css) %&gt; </code></pre> <p>In my themes_controller.rb:</p> <pre><code>class ThemesController &lt; ApplicationController respond_to :css ... def show @theme = Theme.find(params[:id]) respond_with @theme end end </code></pre> <p>I have the requisite <code>show.css.erb</code> file in <code>views/themes</code>.</p> <p>My main issue is that <code>/themes/1?format=css</code> loads and renders the CSS file correctly. However, <code>/themes/1.css</code> – the form of URL generated by the <code>theme_path</code> helper – is producing a 404.</p> <p>I'm probably overlooking something <em>very</em> simple here – hopefully a fellow SO user can point out the bloomin' obvious to prevent my head and brick walls becoming better acquainted...</p> <p><strong>UPDATE:</strong> Doing a bot of Rails route recognition debugging:</p> <pre><code>r = Rails.application.routes #=&gt; #&lt;ActionDispatch::Routing::RouteSet:0x007fc385016170&gt; r.recognize_path '/themes/1.css' #=&gt; {:action=&gt;"show", :controller=&gt;"themes", :id=&gt;"1", :format=&gt;"css"} r.recognize_path '/themes/1?format=css' #=&gt; {:action=&gt;"show", :controller=&gt;"themes", :id=&gt;"1"} </code></pre> <p>So the fact that <code>?format=css</code> seems to be working is actually because, at least when CURLing from the command line, <code>/themes/1</code> is returning the requisite CSS. As far as I'm concerned, that's a red herring...</p> <p>Incidentally, adding this line to <code>routes.rb</code> works:</p> <pre><code> get '/themestyle/:id' =&gt; 'themes#show', as: 'themestyle', format: 'css' </code></pre> <p>(using a slightly different route so as not to conflict with the <code>resources :themes</code> in routes.rb). <code>themestyle_path(current_theme)</code> generates a workable route of – <code>/themestyle/1</code> – I can add the 'text/css' type header at render stage no problem. I'll have to hand-code a <code>&lt;link rel="stylesheet"&gt;</code> element though, as stylesheet_link_tag adds the css suffix.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USScott Matthewman
    1. USScott Matthewman
    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. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POCustom CSS via controller returning via #show/n?format=css but not #show/n.css
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI just tested out a few things on a local server, and with standard routes, going to `/themes/1.css` resolves correctly to the theme show route with format css. Whats your route file look like for the themes?
      singulars
      1. POCustom CSS via controller returning via #show/n?format=css but not #show/n.css
      1. USMichael Lynch
    2. COHi Michael – I was just using `resources :themes`. And you're right, that URL is correctly resolving. But I'm getting a Not Found returning back when actually requesting the URL – and it doesn't even seem to hit the server, according to the local logs...
      singulars
      1. POCustom CSS via controller returning via #show/n?format=css but not #show/n.css
      1. USScott Matthewman
    3. COInteresting that the logs wouldn't even show a request being made, are you sure its requesting from the correct domain?? (Not sure how you could accidentally request from another domain, but thats my only thought as to why the local logs aren't showing a request)
      singulars
      1. POCustom CSS via controller returning via #show/n?format=css but not #show/n.css
      1. USMichael Lynch
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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