Could be related to notch8/hykuup_knapsack#619
I’ve double-checked this a few times and I’m still a bit confused, so I’d really appreciate a second set of eyes.
I’ve verified that the banner image files are in the expected location, and I can open them directly in the browser at:
https://digitalcollections.lib.utk.edu/uploads/56e0eb81-c2d5-4d5d-9171-b251bf7299a4/site/banner_images/1/canvastopincrease.jpg
So the app is serving them from /uploads/....
However, in the rendered page, the CSS is referencing a different path:
background-image: url('/app/samvera/uploads/56e0eb81-c2d5-4d5d-9171-b251bf7299a4/site/banner_images/1/canvastopincrease.jpg');
It looks like the app is “expecting” the files under /app/samvera/uploads/..., even though they’re accessible under /uploads/.... That mismatch feels like the root issue.
I’ve also pulled the images down locally and am working on disabling the cleanup job so we don’t lose any additional files while we sort this out.
Can someone help me understand why the CSS is generating the /app/samvera/uploads/... path instead of /uploads/...? I’d like to make sure we’re fixing the correct layer (asset pipeline? storage config? container path leakage?) and not missing something obvious.
The image exists and is accessible directly, but the app still isn’t serving it correctly in the page. Am I overlooking anything?
[2:44 PM]I can manually change the address in the devtools css and the site then displays them...
Could be related to notch8/hykuup_knapsack#619
I’ve double-checked this a few times and I’m still a bit confused, so I’d really appreciate a second set of eyes.
I’ve verified that the banner image files are in the expected location, and I can open them directly in the browser at:
https://digitalcollections.lib.utk.edu/uploads/56e0eb81-c2d5-4d5d-9171-b251bf7299a4/site/banner_images/1/canvastopincrease.jpg
So the app is serving them from /uploads/....
However, in the rendered page, the CSS is referencing a different path:
background-image: url('/app/samvera/uploads/56e0eb81-c2d5-4d5d-9171-b251bf7299a4/site/banner_images/1/canvastopincrease.jpg');
It looks like the app is “expecting” the files under /app/samvera/uploads/..., even though they’re accessible under /uploads/.... That mismatch feels like the root issue.
I’ve also pulled the images down locally and am working on disabling the cleanup job so we don’t lose any additional files while we sort this out.
Can someone help me understand why the CSS is generating the /app/samvera/uploads/... path instead of /uploads/...? I’d like to make sure we’re fixing the correct layer (asset pipeline? storage config? container path leakage?) and not missing something obvious.
The image exists and is accessible directly, but the app still isn’t serving it correctly in the page. Am I overlooking anything?
[2:44 PM]I can manually change the address in the devtools css and the site then displays them...