Theme Development: Compiling SASS files including paths


In my SCSS files, there are references to external assets like images and fonts. When I compile the styles via the terminal, the paths make sense as the output CSS file is written on /css/skins/default.css. Yet when site editors use the theme customizer, the rendered file is outputted on /application/files/presets/test-1.css, therefore all paths become invalid.

Is there a solution to this problem? maybe a variable that can be added in front of all paths to generate an absolute path?

Hi @shahroq - not off the top of my head, but let me poke around.

So the issue might be that in your compiled css before the customizer the paths are relative - does that ring any bells?

Hi @EvanCooper
Thank you for taking a look at this.

My first approach was using the relative path, and then when the editor uses the core customizer it breaks the path.

Then I switched to the absolute path, which definitely raised fewer complaints, but still, it breaks when the concrete is installed in any place other than the web server root. Check the last msg on this thread for example.

Got it - let me take another look.