Unable to use @import in SCSS

[griffen ★]

Hi,

I have a brand new computer. I have only installed Dreamweaver and a few other Adobe products, I have not installed any Ruby by myself or anything.

In my Dreamweaver site, I am using SCSS. The SCSS compiles when I save the file, and it works just fine mostly.

However, when I add an import, it doesn't compile.

For example, if I put this line: "@import 'assets/styles/reset';" then I get an error.

This is the error

C:/Program Files/Adobe/Adobe Dreamweaver CC 2018/ruby/lib/ruby/gems/2.4.0/gems/sass-3.5.3/lib/sass/importers/filesystem.rb:152: [BUG] Segmentation fault

How can I be able to import using the Dreamweaver SCSS compiler?

Thanks.

[BenPleysier]

Have you added a leading underlying dash to the partials?

For example, if you have

@import "bootstrap";

@import "mystyles";

@import "font-awesome";

the partials will be named

_bootstrap.scss

_mystyles.scss

_font-awesome.scss

[griffen ★]

Hi,

Yes. The file I want to import is called _reset.scss and it is located in this relative path assets/styles/_reset.scss.

Here is my directory of my site.

[BenPleysier]

Did you include the file, assets/styles/_reset.scss, as

@import "styles/reset";

[griffen ★]

No, I used this code:

@import "assets/styles/reset";

The file I am importing from is called style.scss, and it is not in the assets folder.

Even if I put them in the same directory and only write @import "reset"; I still get the same error.

I am very seasoned with SCSS and have never encountered an issue like this on my previous computer, a Mac.

[BenPleysier]

This is what I have and it works without any probs.

[griffen ★]

That's good to know that it works for some people.

Is there a way to fix whatever has broken on my computer? I have even tried uninstalling and reinstalling Dreamweaver, and the problem persists.

[BenPleysier]

Please paste the full error message and Backtrace here

[griffen ★]

Hi,

In my original post I have pasted the error message.

C:/Program Files/Adobe/Adobe Dreamweaver CC 2018/ruby/lib/ruby/gems/2.4.0/gems/sass-3.5.3/lib/sass/importers/filesystem.rb:152: [BUG] Segmentation fault

You can also see a screenshot in my previous post, it has the error message in the bottom area next to a red X.

I do not know how to view the backtrace in Dreamweaver, clicking or double clicking on the error does not reveal any more detail.

Thank you for your help

[BenPleysier]

I repeat: Please paste the full error message and Backtrace here

Edit: Sorry I did not see that you did not know where to find the backtrace. I had the impression that you were well versed in SCSS and therefore assumed that this would be second nature. To get to the point, the Bactrace can be found in the resultant CSS file as in

[griffen ★]

Hi,

Would you kindly explain to me how to view the Backtrace so that I may paste it here?

Thanks

[griffen ★]

Hi,

The error occurs somewhere before a CSS file is generated. Therefore, there is not resultant CSS file to copy backtrace from.

I would also like to mention that if I open the project in another program, such as PHP Storm or even just use the command line program for SCSS I can successfully compile CSS; the errors is not in my code but with the Dreamweaver.

Thanks for your help again

[BenPleysier]

I have tried all sorts of stupid things and cannot replicate the problem. It is time to call in the assistance of Preran​. Being a weekend, it may be a day or so before he answers. Please be patient.

[Preran]

Thank you for the shout, Ben.

Griffen: Let me know if you continue to face this issue. I will have someone from the team drop by and take a look.

Thanks,

Preran

[griffen ★]

If I create style.scss and foo.scss, they both will then have style.css and foo.css created. Inside foo.scss, I put this code:

body { background-color: purple; }

the foo.css properly reflects that.

In style.scss, I tried @import "foo.scss"; but I received the same segmentation fault bug/error as before. I can import foo.css successfully, but that is not what I want to do.

Thanks

[B i r n o u]

it seems so that you have a problem with the installation compiler

[griffen ★ · Accepted solution]

Hi all

I just wanted to let you know I have found an answer.

The site was saved in a OneDrive folder.

Having a site not on OneDrive works just fine.

I found this answer on PhpStorm technical support website and it works for Dreamweaver as well.

Thanks

[B i r n o u]

it is very strange because I never encounter trouble either when working on cloud... can you do a test making your path that way

@import './assets/styles/reset';

[griffen ★]

Hi,

Thanks for your suggestion. Unfortunately, that path didn't work on the OneDrive folder either, producing the same error.

Thanks

[BenPleysier]

Thank you for the feedback, great that it is now working. It goes to show that, if you had mentioned OneDrive to start with, we would have arrived at the solution a lot quicker especially when you say

https://forums.adobe.com/people/griffen+%E2%98%85  wrote

I would also like to mention that if I open the project in another program, such as PHP Storm or even just use the command line program for SCSS I can successfully compile CSS; the errors is not in my code but with the Dreamweaver.

[griffen ★]

I hadn't even noticed the project was on OneDrive as my computer had been automatically set up to use OneDrive for the Documents folder.

To be honest, your responses often had a very patronising tone and it made me very uncomfortable posting in this forum. Anyway, I guess it shows even the most knowledgeable don't know everything.

[BenPleysier]

https://forums.adobe.com/people/griffen+%E2%98%85  wrote

To be honest, your responses often had a very patronising tone and it made me very uncomfortable posting in this forum. Anyway, I guess it shows even the most knowledgeable don't know everything.

Please explain, I am willing to listen and amend my ways.

[griffen ★]

Edit: Sorry I did not see that you did not know where to find the backtrace. I had the impression that you were well versed in SCSS and therefore assumed that this would be second nature. To get to the point, the Bactrace can be found in the resultant CSS file as in

Comments like these are not conducive to the conversation and only serve to be rude.

Had there in fact been a resultant CSS file for me to follow the errors in, it might've been altogether unnecessary for this thread to exist, as it would be my first attempt to solve the problem by seeing where something went wrong in my code. But, you write this comment which makes me feel dumb, when in reality the issue was with the Dreamweaver and nothing at all with my code.

[BenPleysier]

https://forums.adobe.com/people/griffen+%E2%98%85  wrote

I am very seasoned with SCSS and have never encountered an issue like this on my previous computer, a Mac.

Ok. I misread the above. My apologies.

[griffen ★]

You didn't misread that. While I am very experienced with using SCSS, I am new to Windows. Dreamweaver didn't have any issues using iCloud on my Mac.

I hope these condescending replies are not representative of Adobe support. I know you are not an official employee but you are still representing them with the title of ACP; I am seriously considering cancelling my subscription if I have to expect to be treated so unprofessionally when trying to receive assistance with a product I pay so much money for.