-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Hacsfiles path for theme images resulting in 404 #3751
Comments
Make sure you have read the issue guidelines and that you filled out the entire template. If you have an issue identical to this, do not add comments like "same here", "i have this too", instead add a 👍 reaction to the issue description. Thanks! 👍 |
Yes, that is correct. |
Thanks for the response @ludeeus. Is there a recommended alternative besides copying the image files out of the theme to www and modifying the theme to point to them? |
There are 3 options:
|
Got it, thanks for the details! |
System Health details
System Information
Home Assistant Community Store
keymaster
Dashboards
Recorder
Spotify
Checklist
Describe the issue
Theme images no longer seem to be provided through the hacsfiles url. For example, the path
/hacsfiles/themes/ios-themes/homekit-bg-blue-red.jpg
(utilized by this theme for it's background image) results in a 404.I've done a lot of Home Assistant upgrade work over the past week (I was running 2023.12 previously) and didn't notice exactly which step the image disappeared with (since it was cached by the browser). I believe it has to do with experimental mode since another Home Assistant instance I have running the same version of core (2024.4.4) and HACS (1.34.0) isn't running experimental mode.
Is it expected that HACS no longer provides that path for theme images running in experimental mode?
Reproduction steps
themes/ios-themes
pathios-dark-mode-blue-red
/hacsfiles/themes/ios-themes/homekit-bg-blue-red.jpg
via browser or curl and confirm that you get a 404 instead of the image file....
Debug logs
The text was updated successfully, but these errors were encountered: