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
Which exact Umbraco version are you using? For example: 8.13.1 - don't just write v8
9.00
Bug summary
Using the file picker, if you pick a file within 'wwwroot' for example a stylesheet. It will try and reference the stylesheet including the wwwroot folder.
If you create a Block List editor and create a block within it, then in the editor appearance section, select your stylesheet from the wwwroot (i.e. /wwwroot/css/styles.css) this whole path gets saved. And when you try to load the block view from the content section it fails because the .css file needs to be served from the root and not 'wwwroot'
YodasMyDad
changed the title
Issue with file picker and referencing files from wwwroot returns 404
v9 - Issue with file picker and referencing files from wwwroot returns 404
Sep 30, 2021
Which exact Umbraco version are you using? For example: 8.13.1 - don't just write v8
9.00
Bug summary
Using the file picker, if you pick a file within 'wwwroot' for example a stylesheet. It will try and reference the stylesheet including the wwwroot folder.
i.e. https://localhost:44361/wwwroot/css/styles.css
However, this results in a 404 not found. Because all files in wwwroot have to be served from the root. https://localhost:44361/css/styles.css
Specifics
No response
Steps to reproduce
If you create a Block List editor and create a block within it, then in the editor appearance section, select your stylesheet from the wwwroot (i.e. /wwwroot/css/styles.css) this whole path gets saved. And when you try to load the block view from the content section it fails because the .css file needs to be served from the root and not 'wwwroot'
Wrong
https://localhost:44361/wwwroot/css/styles.css
Correct
https://localhost:44361/css/styles.css
Expected result / actual result
No response
The text was updated successfully, but these errors were encountered: