Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

Dreamweaver CC 2017 won't properly compile sass files into output directory

New Here ,
Feb 17, 2017 Feb 17, 2017

Now that Dreamweaver has support for SASS, I'm trying to use it to manage files for a web application, but a project structure that works perfectly in Scout is seemingly invalid inside of Dreamweaver. I want to believe it's user error, but I can't figure it out.

The project was originally built with a flat css file, but I'm trying to update things a bit.

folder structure.png

Ultimately, I want the compiled CSS files to go into resources/META-INF/styles, but I want to store the SASS files in resources/sass.

source settings.PNG

I've got my source and output folders defined as shown above (I stripped out a lengthy site root for readability).

At this point, when I attempt to compile a sass file, I get the following error:

error.png

Everything looks right according to the settings I've defined:

snips.png

If I dump the contents of my sass directory into the styles directory and then set my source and output folders to be the site's root, it compiles just fine, but I don't want to clutter the styles folder with sass files unnecessarily.

Also: If I setup this project in Scout using my desired folder structure, it compiles as expected, so I have a workaround, but I'd really like to eliminate the extra step of running Scout every time I modify the CSS, because Dreamweaver should be able to handle this (if I can figure out how to set it up correctly).

792
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Feb 17, 2017 Feb 17, 2017

The way that you have linked 'baseStyles' in fileManager.scss is not correct.

Try @import "../common/baseStyles"

Wappler is the DMXzone-made Dreamweaver replacement and includes the best of their powerful extensions, as well as much more!
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Feb 17, 2017 Feb 17, 2017
LATEST

That's not exactly the answer I'd hoped for, but it's better than nothing. I'll give it a try when I get back to work.

As mentioned, the file compiles perfectly as is running Scout with the same input and output settings.

Plus, I'm reasonably certain that "../" would evaluate to the same link I've already defined if used in other contexts (like a src for a script tag or an include in PHP). So it should work here too.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines