You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When upgrading from sprockets-rails 3.2.2 to 3.4.1 or 3.4.2, font awesome font urls are incorrectly fetched in production. Unfortunately I haven't been able to reproduce in development.
To reproduce, install an affected version of sprockets, start a production server and visit the admin panel. Icons in the sidebar will not render. In the devtools network panel, font awesome urls will show 404. Click on one, and you should see:
Expected
my-host/font-awesome-url.woff2
Actual
my-host/my-host/font-awesome-url.woff2
@texpert you did some work on non-digest assets, would you be able to take a look at this as well? I have a feeling you might be able to figure this out faster than me 😃
Known affected versions of sprockets-rails:
3.4.1
3.4.2
Known unaffected versions of sprockets-rails:
3.2.2 and below
The text was updated successfully, but these errors were encountered:
Thanks @texpert for looking at this. I tried version 3.4.2 again while also expiring my assets and all seems to be well with that small change. 3.4.2 must have been caching the bad urls that were built with the problematic version 3.4.1. I would have chased that around all day if you hadn't responded that it worked in your case.
When upgrading from sprockets-rails 3.2.2 to 3.4.1 or 3.4.2, font awesome font urls are incorrectly fetched in production. Unfortunately I haven't been able to reproduce in development.
To reproduce, install an affected version of sprockets, start a production server and visit the admin panel. Icons in the sidebar will not render. In the devtools network panel, font awesome urls will show 404. Click on one, and you should see:
@texpert you did some work on non-digest assets, would you be able to take a look at this as well? I have a feeling you might be able to figure this out faster than me 😃
Known affected versions of sprockets-rails:
Known unaffected versions of sprockets-rails:
The text was updated successfully, but these errors were encountered: