![server filewatcher to recompile sass server filewatcher to recompile sass](https://dev.macha795.com/wp-content/uploads/2020/02/2020-02-19_13-22-57_974762-20200218-122659-auto-sass-less.jpg)
#Server filewatcher to recompile sass code
I add some new code in partials/_test.sass saving several times.I add "partials/test" to subtheme.scss and save.I created _test.sass in my subtheme/sass/partials folder, add some code, and save.
#Server filewatcher to recompile sass update
My question would be, does Assetic compile a production css file if I update a partial, but don't touch the subtheme.scss? It seems as though my "partials" changes only show up if I resave the subtheme.scss You mentioned earlier that debug shouldn't be necessary for the page refreshes. One other thing, while I'm still thinking about the whole partials thing. Note that the salsa settings file does not define sidebars, which is where the error is coming from. Your css will only outputs !default values (defined in sites/all/themes/sasson/sass/salsa/sass/_settings.scss), instead of sasson's or your subtheme's overrides.
![server filewatcher to recompile sass server filewatcher to recompile sass](https://i.imgur.com/a34PJSd.jpg)
What OS are you on ? what version of compass ? did you get your custom styles, other than the layout, to compile ? info file - well, those theme settings are just the default settings, you can change them before you enable the theme but once you did - those go into the DB and changes in the file will be ignored.īut I still can't see why changes in your theme settings form are ignored. all in all your settings sound good.Ībout the. you should have "debugging" turned on only on extreme cases where you are testing the compiler (and now we are, but don't forget to turn it off) this might also be related to the fact that the file watcher choked your server though I'm not sure why. So, about your settings, nothing special here. Settings = 'sites/all/themes/hlr_sasson/styles/hlr_sasson.scss' Settings = 'ul#main-menu-links, ul#secondary-menu-links' sub-themes must re-declare default settings. these are the defaults for the theme settings configuration. Similar in output paths to refresh: $FileParentDir$/css/$FileNameWithoutExtension$.css:$FileParentDir$/css/$FileNameWithoutExtension$.css.Just for fun, here's the.
![server filewatcher to recompile sass server filewatcher to recompile sass](https://buldenkov.ru/upload/medialibrary/e39/2018_05_30_09_46_03.png)
(set the css in the css subfolder of the parent directory) In arguments I use: $FileName$:$FileParentDir$/css/$FileNameWithoutExtension$.css
![server filewatcher to recompile sass server filewatcher to recompile sass](https://upload-images.jianshu.io/upload_images/7661680-172c9916788a3bef.png)
If you want scss files in one folder and css in another this structure might be similar to mine: theme To select the program you can set sass.cmd and find it in your appdata folder of your user accout (\AppData\Roaming\npm\sass.cmd) Make sure the pattern line is empty and navigate to your theme folder, select it en press the button ‘include recursively’.Behind the value of the scope line click the 3 dots.Select SCSS to open the settings for a newly scss file watcher.Press ‘ctrl + alt + s’ to open options, search for ‘File Watcher’ and press the ‘+’ top right.We only want files in our theme folder compiled, not in the WooCommerce folder, or any other*. Here is how I did it:Īdded 15 packages from 18 contributors in 0.844s But I have switched, and now with pleasure I am using PhpStorm to do it for me. In the beginning of working with sccs I used gulp in the commandline to manually run a gulp file, or used screen to have a process running continuesly while using my console for aither things like wp cli.