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
Theme assets not found after precompiling #137
Comments
Chris, where is this error? |
I setup a site for use in production. I'll put an example on heroku. |
I'm deploying a sample app to heroku right now. |
Application source code: https://github.com/cmckni3/camaleon-assets-bug |
Similar problem here. |
Today I will review... |
I believe I figured out part of my problem. I'm going to confirm the fix in another app. PR coming soon as well. |
👍 Looks good on my end. Just had to change the stylesheet link in my theme to |
great! |
Precompilation just finished on my other app and everything is working great with serving assets through nginx. So glad to resolve this issue. 👍 @flaranda Check your theme to make sure you have the extension when referencing the main stylesheet |
Great! Thanks @cmckni3 :) |
No problem @flaranda |
The frontend of the site isn't using the correct path to the theme assets. It should use the path
/public/assets/themes/[theme-name]/assets/css
but it only get/public/assets/css
I set
serve_static_files
totrue
andassets.compile
tofalse
. For now, I enabled compilation and disabled serving static files but this needs to be investigated.The text was updated successfully, but these errors were encountered: