using 3.1.0.rc5 (though same thing happened on rc4), asset pipeline is loaded with blueprint css (I just dumped it all into a sub-directory and loaded it in the manifest).
All of my show something like (href)… so for <a href"/my/page">woot it renders woot (/my/page)…
Anybody know WTH? Its gotta have something to do with blueprint, right? I thought it may be that “button as icons” plugin, though I deleted that out and restarted the server (thinking that sprockets does some caching or something) and nada.
using 3.1.0.rc5 (though same thing happened on rc4), asset pipeline is
loaded with blueprint css (I just dumped it all into a sub-directory and
loaded it in the manifest).
All of my show something like <text> (href)... so for <a
href"/my/page">woot</a> it renders woot (/my/page)....
Comment the part where you include the application.css in your application.html.erb.
I had the same problem, as I was also using blueprint-css.
Hope it helps.
Yeah…typo on my part (links are naturally auto-generated and fine)…
Its deffinetly blueprint.css… I moved it out to vendor/assets/stylesheets though I’m at a loss on how to “require” it… I thought sprockets has that in its load path (according to http://ryanbigg.com/guides/asset_pipeline.html) though it doesn’t seem to be picking up anything there… (though my links are fine without blueprint there
… huh… oh well. I’m still a little puzzled as to the sprockets load path dealie…
I would think that anything in app/assets/** is supposed to be there IF it requires processing (.coffee, .scss, .erb). Though I couldn’t find any resources out there on how to manage the manifest files to load the static asset files in lib/assets and vendor/assets.
