-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Asset Pipeline Could Not Find Stylesheet #45
Comments
The console output was pretty much spot on to the console output in #42 |
Can you verify the HTML output? Add a |
Sorry @Mange this looks like a serious case of Gremlins. VERY BIZARRE. |
I'm glad it worked our for you. ☺ ons 12 aug 2015 04:59 Jaymie Jones notifications@github.com skrev:
|
having the same issue here if I remove the require_self line in mail.css the errors move on the next require line. |
I was also having a similar problem:
I traced it to updating sass-rails from 4.0.5 to 5.0.4 (sass-rails 5.0.4 brings in a much newer sprockets as well), reverting sass-rails to 4.0.5 fixed the issue for me. |
This is clearly something I need to investigate now. Thanks for the extra details! Den lör 12 mars 2016 08:42Weston Triemstra notifications@github.com skrev:
|
Can confirm this one too. Should specs be using compiled assets? |
Running into this problem too. Seems that Roadie is looking for precompiled assets in the test environment. |
that was any development in this matter? I'm experiencing the issue. |
Sorry, I forgot about this. Since the gem is now in passive maintenance mode, I'm waiting for someone else to find the cause and propose a fix. I'm not using this gem myself, and in the Rails app I'm currently passively maintaining, we don't use the asset pipeline anyway. The issue seems to be how the gem tries to auto-detect that asset pipeline is enabled before it adds the provider for live-compiled assets. That probably fails because some option was moved around, which makes it only pick the pre-compiled assets provider. Worst-case, you could just manually add the right provider in your config and stop relying on the auto-detection. |
I am using the automatic processing of emails in a Rails 4.2.3 app and am running into the following issue (note, I have seen similar issues but I think mine may be slightly different):
This error is happening in production and development, it seems the hash is different.
In development when I compile the assets, the path is right but the hash is different.
Notice how
self
is in the version by roadie?The email stylesheet is being loaded in at:
The text was updated successfully, but these errors were encountered: