I've run into an error with the Rails 3.1 asset pipeline where one of my controllers happens to be named AssetsController:
No route matches {:action=>"show", :controller=>"assets", :id=>"web-app-theme/base", :format=>"css", nil=>:request}
Hmmm. What to do? First, an explanation.
Here's what's happening:
I figure there are a few options:
Ultimately it seems that the nexus of this problem is that the tag helpers do not use the custom config.assets.prefix value. Thankfully, there has been a commit to fix it. Alas, it seems to have been overlooked in recent tags and releases.
As a quick workaround, I'm not using the tag helpers, just accessing the css files directly.
UPDATE: Hooray! Rails developer spastorino pulled request 3092 to fix this issue. That is so great. FWIW - my initial experience working with the Rails development community has been positively impressive.
¥