# unable to open .design file after adding bstudio-sass path to Design settings **URL:** \ **Category:** Bug Reports\ **Created:** [March 6, 2018, 7:06pm UTC](https://forum.bootstrapstudio.io/t/unable-to-open-design-file-after-adding-bstudio-sass-path-to-design-settings/4181 "2018-03-06T19:06:22Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![scott-g](https://forum.bootstrapstudio.io/letter_avatar_proxy/v4/letter/s/7ba0ec/32.png) [@scott-g](https://forum.bootstrapstudio.io/u/scott-g)\ **Post date:** [March 6, 2018, 7:06pm UTC](https://forum.bootstrapstudio.io/t/unable-to-open-design-file-after-adding-bstudio-sass-path-to-design-settings/4181/1 "2018-03-06T19:06:22Z")
https://bootstrapstudio.io/tutorials/writing-sass I followed the instructions here, got the path response from the npm app, and added it to the Design settings, and restarted. now when I try and open the file it just gives me "An error occurred while reading this design. It can't be opened." no possibility of recovery, and no way to edit out the setting I just made. no backup. OUCH ! DAYS of work down the drain.. is there any chance you would be able to assist in the recovery of this file and undo that last Design Setting change, and remove that path from the file? I can live without scss, for now, and would REALLY appreciate not having to re-do all the work I did on this design up to this point ---
**Author:** ![scott-g](https://forum.bootstrapstudio.io/letter_avatar_proxy/v4/letter/s/7ba0ec/32.png) [@scott-g](https://forum.bootstrapstudio.io/u/scott-g)\ **Post date:** [March 6, 2018, 7:17pm UTC](https://forum.bootstrapstudio.io/t/unable-to-open-design-file-after-adding-bstudio-sass-path-to-design-settings/4181/2 "2018-03-06T19:17:05Z")
I've provided a [Dropbox Download of the bsdesign file](https://www.dropbox.com/s/yxdkd9hh49gtxvv/Airgreen,%20Inc..bsdesign?dl=0) in the hopes of gaining any assistance ---
**Author:** ![scott-g](https://forum.bootstrapstudio.io/letter_avatar_proxy/v4/letter/s/7ba0ec/32.png) [@scott-g](https://forum.bootstrapstudio.io/u/scott-g)\ **Post date:** [March 6, 2018, 7:30pm UTC](https://forum.bootstrapstudio.io/t/unable-to-open-design-file-after-adding-bstudio-sass-path-to-design-settings/4181/3 "2018-03-06T19:30:57Z")
Node version v6.12.0 (currently still on Fedora 25) NPM version 5.7.1 I'm attempting to compile nodejs-8.9.3-2.fc27.src.rpm for my system (which is the latest available to me that will still compile on this version of Fedora) to see if this is at the heart of the issue. will report back. ---
**Author:** ![scott-g](https://forum.bootstrapstudio.io/letter_avatar_proxy/v4/letter/s/7ba0ec/32.png) [@scott-g](https://forum.bootstrapstudio.io/u/scott-g)\ **Post date:** [March 6, 2018, 8:21pm UTC](https://forum.bootstrapstudio.io/t/unable-to-open-design-file-after-adding-bstudio-sass-path-to-design-settings/4181/4 "2018-03-06T20:21:57Z")
regrettably I am unable to compile the latest nodeJS on my system from the more recent Fedora RPM's -- short of updating my entire system, I'm stuck. The .bdesign archive itself seems fine -- I am able to gunzip it to its natural state, and read the file cleanly, but am unable to find the setting that alters the scss path to remove the offending bit that I believe to be causing the error -- perhaps some enterprising person can offer suggestions in that regard? ---
**Author:** ![scott-g](https://forum.bootstrapstudio.io/letter_avatar_proxy/v4/letter/s/7ba0ec/32.png) [@scott-g](https://forum.bootstrapstudio.io/u/scott-g)\ **Post date:** [March 6, 2018, 9:43pm UTC](https://forum.bootstrapstudio.io/t/unable-to-open-design-file-after-adding-bstudio-sass-path-to-design-settings/4181/5 "2018-03-06T21:43:23Z")
``` ~/madhouse/airgreen/site/www/devel/test (master)>$ ls .. 'Airgreen, Inc..bsdesign' test/ ~/madhouse/airgreen/site/www/devel/test (master)>$ cat ../Airgreen\,\ Inc..bsdesign |gunzip - > airgreen.json ~/madhouse/airgreen/site/www/devel/test (master)>$ json_verify < airgreen.json JSON is valid ~/madhouse/airgreen/site/www/devel/test (master)>$ python -c 'import sys,yaml,json; yaml.safe_dump(json.load(sys.stdin),sys.stdout, default_flow_style=False)' < airgreen.json > airgreen.yaml ~/madhouse/airgreen/site/www/devel/test (master)>$ python -c 'import yaml,sys;yaml.safe_load(sys.stdin)' < airgreen.yaml ~/madhouse/airgreen/site/www/devel/test (master)>$ ``` clearly the file itself is valid JSON and appears generally uncorrupted. The error message itself is hugely uninformative, and the lack of any sort of console or debugging mode for Bootstrap Studio itself leaves me completely in the dark as to the exact nature of the failure of this file to open properly. Is there any way to get Bootstrap Studio to emit debug messages to the commandline so we can find out what's going on here? ---
**Author:** ![wasyl](https://forum.bootstrapstudio.io/user_avatar/forum.bootstrapstudio.io/wasyl/32/378_2.png) [@wasyl](https://forum.bootstrapstudio.io/u/wasyl)\ **Post date:** [March 7, 2018, 8:32am UTC](https://forum.bootstrapstudio.io/t/unable-to-open-design-file-after-adding-bstudio-sass-path-to-design-settings/4181/6 "2018-03-07T08:32:26Z")
I have similar problem. Can't open the .bsdesign file ---
**Author:** ![marrco](https://forum.bootstrapstudio.io/letter_avatar_proxy/v4/letter/m/e95f7d/32.png) [@marrco](https://forum.bootstrapstudio.io/u/marrco)\ **Post date:** [March 7, 2018, 9:19am UTC](https://forum.bootstrapstudio.io/t/unable-to-open-design-file-after-adding-bstudio-sass-path-to-design-settings/4181/7 "2018-03-07T09:19:15Z")
If yours is a legit install contact the developer. I'm sure he's interested in ironing out this issue ---
**Author:** ![martin](https://forum.bootstrapstudio.io/user_avatar/forum.bootstrapstudio.io/martin/32/3_2.png) [@martin](https://forum.bootstrapstudio.io/u/martin)\ **Post date:** [March 7, 2018, 9:33am UTC](https://forum.bootstrapstudio.io/t/unable-to-open-design-file-after-adding-bstudio-sass-path-to-design-settings/4181/8 "2018-03-07T09:33:17Z")
Thank you for reporting this bug and including your bsdesign! We will release a fix later today. ---
**Author:** ![scott-g](https://forum.bootstrapstudio.io/letter_avatar_proxy/v4/letter/s/7ba0ec/32.png) [@scott-g](https://forum.bootstrapstudio.io/u/scott-g)\ **Post date:** [March 7, 2018, 1:51pm UTC](https://forum.bootstrapstudio.io/t/unable-to-open-design-file-after-adding-bstudio-sass-path-to-design-settings/4181/9 "2018-03-07T13:51:50Z")
Thanks for the quick response, Martin. Looking forward to the fix and not having to re-do my efforts. ---
**Author:** ![martin](https://forum.bootstrapstudio.io/user_avatar/forum.bootstrapstudio.io/martin/32/3_2.png) [@martin](https://forum.bootstrapstudio.io/u/martin)\ **Post date:** [March 7, 2018, 4:42pm UTC](https://forum.bootstrapstudio.io/t/unable-to-open-design-file-after-adding-bstudio-sass-path-to-design-settings/4181/10 "2018-03-07T16:42:27Z")
We launched version 4.1.4 which should fix this. Do write once you try it out. ---
**Author:** ![scott-g](https://forum.bootstrapstudio.io/letter_avatar_proxy/v4/letter/s/7ba0ec/32.png) [@scott-g](https://forum.bootstrapstudio.io/u/scott-g)\ **Post date:** [March 7, 2018, 5:13pm UTC](https://forum.bootstrapstudio.io/t/unable-to-open-design-file-after-adding-bstudio-sass-path-to-design-settings/4181/11 "2018-03-07T17:13:48Z")
I can open the file, now. (thanks!) but am now getting "Sass compliation error. Make sure that bstudio-sass tool from npm is installed" it definitely is installed and the path in the Design Settings is correct. also I've put some scss content in the file so it is no longer empty (defined a few variables), and still getting the same error message ---
**Author:** ![scott-g](https://forum.bootstrapstudio.io/letter_avatar_proxy/v4/letter/s/7ba0ec/32.png) [@scott-g](https://forum.bootstrapstudio.io/u/scott-g)\ **Post date:** [March 9, 2018, 7:36pm UTC](https://forum.bootstrapstudio.io/t/unable-to-open-design-file-after-adding-bstudio-sass-path-to-design-settings/4181/12 "2018-03-09T19:36:38Z")
The problem was appaently due to the older version of Node on my system. I was able to get around the problem by using [NVM (node version manager)](https://github.com/creationix/nvm) which let me selectively override the system's install (Fedora 25) as needed and work with multiple versions of Nodejs if need be (pretty cool) (so I could have the system version, the LTS 8.10.x and the bleeding edge 9.8.x all at the same time) I just wanted to follow up with this post, so that there's a record of what can be done to resolve this for others who may encounter the same issue ---
**Author:** ![siarhei](https://forum.bootstrapstudio.io/letter_avatar_proxy/v4/letter/s/90db22/32.png) [@siarhei](https://forum.bootstrapstudio.io/u/siarhei)\ **Post date:** [March 20, 2018, 12:52pm UTC](https://forum.bootstrapstudio.io/t/unable-to-open-design-file-after-adding-bstudio-sass-path-to-design-settings/4181/13 "2018-03-20T12:52:38Z")
Please update download links for linux versions too. There is still version 4.0.4. ---
**Author:** ![scott-g](https://forum.bootstrapstudio.io/letter_avatar_proxy/v4/letter/s/7ba0ec/32.png) [@scott-g](https://forum.bootstrapstudio.io/u/scott-g)\ **Post date:** [March 20, 2018, 3:22pm UTC](https://forum.bootstrapstudio.io/t/unable-to-open-design-file-after-adding-bstudio-sass-path-to-design-settings/4181/14 "2018-03-20T15:22:24Z")
Which download links are you referring to? what url? ---
**Author:** ![siarhei](https://forum.bootstrapstudio.io/letter_avatar_proxy/v4/letter/s/90db22/32.png) [@siarhei](https://forum.bootstrapstudio.io/u/siarhei)\ **Post date:** [March 21, 2018, 8:21pm UTC](https://forum.bootstrapstudio.io/t/unable-to-open-design-file-after-adding-bstudio-sass-path-to-design-settings/4181/15 "2018-03-21T20:21:12Z")
> > Which download links are you referring to? what url? I'm tried all Linux version from bootstrapstudio.io/download page. There is version 4.0.4 ---
**Author:** ![scott-g](https://forum.bootstrapstudio.io/letter_avatar_proxy/v4/letter/s/7ba0ec/32.png) [@scott-g](https://forum.bootstrapstudio.io/u/scott-g)\ **Post date:** [March 22, 2018, 12:43pm UTC](https://forum.bootstrapstudio.io/t/unable-to-open-design-file-after-adding-bstudio-sass-path-to-design-settings/4181/16 "2018-03-22T12:43:02Z")
Well, it will auto-update after the download once you have applied your key, don't forget. ---
**Author:** ![siarhei](https://forum.bootstrapstudio.io/letter_avatar_proxy/v4/letter/s/90db22/32.png) [@siarhei](https://forum.bootstrapstudio.io/u/siarhei)\ **Post date:** [March 22, 2018, 8:50pm UTC](https://forum.bootstrapstudio.io/t/unable-to-open-design-file-after-adding-bstudio-sass-path-to-design-settings/4181/17 "2018-03-22T20:50:19Z")
It is not auto-updated on Linux (Ubuntu 16.04) ---
**Author:** ![scott-g](https://forum.bootstrapstudio.io/letter_avatar_proxy/v4/letter/s/7ba0ec/32.png) [@scott-g](https://forum.bootstrapstudio.io/u/scott-g)\ **Post date:** [March 22, 2018, 9:16pm UTC](https://forum.bootstrapstudio.io/t/unable-to-open-design-file-after-adding-bstudio-sass-path-to-design-settings/4181/18 "2018-03-22T21:16:47Z")
have you pulled the dropdown menu "Check for Updates" and then restarted after it tells you to? ---
**Author:** ![siarhei](https://forum.bootstrapstudio.io/letter_avatar_proxy/v4/letter/s/90db22/32.png) [@siarhei](https://forum.bootstrapstudio.io/u/siarhei)\ **Post date:** [March 22, 2018, 9:36pm UTC](https://forum.bootstrapstudio.io/t/unable-to-open-design-file-after-adding-bstudio-sass-path-to-design-settings/4181/19 "2018-03-22T21:36:06Z")
yes, but it is doesn't update at all ---
**Author:** ![scott-g](https://forum.bootstrapstudio.io/letter_avatar_proxy/v4/letter/s/7ba0ec/32.png) [@scott-g](https://forum.bootstrapstudio.io/u/scott-g)\ **Post date:** [March 26, 2018, 12:32pm UTC](https://forum.bootstrapstudio.io/t/unable-to-open-design-file-after-adding-bstudio-sass-path-to-design-settings/4181/20 "2018-03-26T12:32:25Z")
then I would suggest two things: 1\> start your own bug report forum post rather than tacking on your discussion at the tail end of an unrelated bug report that's already been resolved 2\> ALSO use the dropdown menu under HELP\> Bug Report in the app, to send a message to the developers directly, and reference your forum post URL in that message