# Theme Development: Compiling SASS files including paths

**URL:** https://forums.concretecms.org/t/theme-development-compiling-sass-files-including-paths/6292
**Category:** Developing with Concrete
**Created:** [October 11, 2023, 10:58am UTC](https://forums.concretecms.org/t/theme-development-compiling-sass-files-including-paths/6292 "2023-10-11T10:58:07Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![shahroq](https://forums.concretecms.org/user_avatar/forums.concretecms.org/shahroq/32/5618_2.png) [@shahroq](https://forums.concretecms.org/u/shahroq)
#### Post date: [October 27, 2023, 9:59am UTC](https://forums.concretecms.org/t/theme-development-compiling-sass-files-including-paths/6292/4 "2023-10-27T09:59:19Z")

</div>

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.

> **[Multiple issues - Concrete CMS](https://marketplace.concretecms.com/marketplace/themes/pixel-9/support/multiple-issues/)**
>
> I have encountered a number of issues.
> Firstly the files/folders had incorrect permissions when extracted from zip file via cPanel, see screen grab.
> Customise skin is missing any options with default skin. See screen grab.
> Customised dark skin...

---

_[View the full topic](https://forums.concretecms.org/t/theme-development-compiling-sass-files-including-paths/6292)._