Dreamweaver 2017 won't compile SASS files

[scottCWD]

I have upgraded to DW 2017. (Mac OS X)

I have gone to sites > [the site] > CSS preprocessors > general

and I have selected "enable auto compilation on save"

I have gone to sites > [the site] > CSS preprocessors > source and output

and I have selected the source and output folders to be the same.

I cannot get a css file to compile. I have been using terminal and have recently been using Koala but I would like to use Dreamweaver for this rather than another tool.

Phone support sent me a link to Dreamweaver: Setting up SASS and Compiling the Code - Lena Shore As if I hadn't already researched this on Google myself (for many hours). This link deals with Dreamweaver 2013 and uses CodeKit for compilation so the link is unrelated to my question. He was stumped and told me to contact the forums so here I am. Help please?

Thank you,

Scott

[BenPleysier]

You are right. This is what Using CSS preprocessors in Dreamweaver says:

Less is JavaScript based and Sass is Ruby-based

[B i r n o u]

thanksBen for the heads up, I think to remember a long thread during the first integration of Sass in the prerelease, where ruby was choose to be used instead of libsass.. but then since I've lost some focus on this one... personnaly I use Sass with Ruby from an external process... I can say that I never, never, had any conflict... nor in gulp, grunt, npm... well any node process...

I will be curious to see what was going on there

please Daren, next time (if it happen) think to check from the output windows

[DarrenCrabb]

Will do. I'm just performing another quick scan using 'Managed anti-virus', to see if that might be having any effect.

[DarrenCrabb]

It's just finished the scan and no-ill effects - Dreamweaver still detecting and outputting fine, so that eliminates that one.

[DarrenCrabb]

Hi Birnou,

So, I have the same issue again this morning ... sass not triggering a rewrite of css. I've looked in the output window, nothing at all. With the output window open, made another change and saved it .. .still nothing. Switched to the main scss file, which is basically a list of imports for the partials, made a change on that and saved, nothing.

This seems to be happening on the first launch of Dreamweaver after a machine restart. It was fine for the rest of the day yesterday.

I don't need to actually make any changes to the css at the moment, so I'll leave it in this non-writing state for the purposes of analysing the situation! Let me know if you can think of any other tests I can do to get any further clues on what's going on.

Thanks,

Darren

[B i r n o u]

very strange behavior... if you don't mind the best way could be probably to join the alpha program, that way engineer from Adobe could have a look at your environment et find out what's going on here...

personnaly I use sass under ruby... and I simply have a .bat file on the web site project that I launch... that's it and it works like a charm...

[BenPleysier]

I am probably wrong again, but I now think that node.js is used to connect with the Adobe servers.

[DarrenCrabb]

I don't think it's Gulp as I haven't used Gulp this morning yet. I just thought I'd do a quick test on the CSS before doing too much. Interesting that Dreamweaver is using node.js though, I didn't know that.

[B i r n o u]

what say the output window whne you save a changed sass file ? (Shift F6)

[DarrenCrabb]

I've missed that opportunity now as I've restarted Dreamweaver and all is working normally now - I'll look at it when it next happens. I have notcied that the little one line display under the file list that normally states that stuff has been written doesn't change at all though - it's as if it's not detecting the change.

[B i r n o u]

just curious... if you use gulp to compile small js... use ff to live preview... why are you not adding task to gulp to compile sass... and in the same time watch to automaticaly reload in FF???

[DarrenCrabb]

I'm new to Gulp .. I need to have a look at all the things that I could do with it. I was using Dreamwever to compile SASS before I started using Gulp so didn't look into doing SASS with it. I think I'd rather keep the SASS in Dreamweaver really, as it's easy to switch the output style to expanded/compact etc. without editng a gulp file.

[B i r n o u]

as I said before... I was just curious.. so you did answer me...

[BenPleysier]

You need to change your user name mate! See here Email signatures and personal information