Open aaronstezycki opened 8 years ago
I have the same issue. It started after updating Cactus for mac to use version 3. It looks like the command to process the scss files has changed.
Same here, won't build SASS/SCSS or CoffeeScript files.
Same here on Mac build 1.1.22 (440).
Is this project still active? I know its not 'actively' being worked on... but atleast bug fixes and OS updates should still be maintained? I think its poor from the development team to allow this to happen. At least let us know that the project is no longer running and to find a similar application such as Hammer for Mac?
Hi there,
Are you using the Mac app or the CLI tool?
Also, do you know how those files are supposed to be processed? Are you using any plugins?
Unfortunately, if the problem lies in the Mac app, I'm probably not going to be able of much help : /
Cheers,
@krallin I'm having the issue in the Mac app, so I installed the CLI tool and can run both cactus serve
and cactus deploy
without issue.
Also having the same issue with the Mac app. "find: scss: No such file or directory"
I have tried re-installing the gem without success. Command line works fine.
@krallin Its definitely the mac app, I don't use the CLI tool at all, not much of a Terminal guy, prefer the lazy GUI option. ... It seems it just doesn't wanna build scss files at all. Im running Yosemite 10.10.5 at work, and El Capitan at home. I can't seem to build at all on El Capitan, however at work on Yosemite I can manage it with using Cactus 1.1.15.
In the Mac app, you need to open plugins/default.py and uncomment the SCSS run command in the preBuild function.
def preBuild(site):
pass
# For scss/sass you need to install sassc: brew install sassc
run('find %s -name "*.scss" -not -name "_*" -exec bash -c "sassc \'{}.scss\' > \'{}.css\'" \;' % pipes.quote(site.static_path))
# For coffee script you need to install coffee script: npm install -g coffee-script
# run('find %s -name "*.coffee" -exec coffee -c {} \;' % pipes.quote(site.static_path))
This worked for me at least.
Uncommenting the SCSS run command compiles the scss correctly, but the file name is '.scss.css'. Using the mac app v1.1.22 (440)
I think rewriting plugins/default.py solve these problems.
run('find %s -name "*.scss" -not -name "_*" -exec bash -c "sassc \'{}.scss\' > \'{}.css\'" \;' % pipes.quote(site.static_path))
By the way, there is not the word "sass".
Who can do it?
Use the following (as already mentioned) for scss:
run('find %s -name "*.scss" -not -name "_*" -exec scss -C --update {} \;' % pipes.quote(site.static_path))
and this one for sass:
run('find %s -name "*.sass" -not -name "_*" -exec scss -C --update {} \;' % pipes.quote(site.static_path))
I'm still getting this problem in both the GUI and the CLI after updating from Yosemite to El Capitan.
find: scss: No such file or directory
My default.py has the following:
def preBuild(site): run('find %s -name "_.scss" -not -name "__" -exec scss -C --update {} \;' % pipes.quote(site.static_path))
Anyone figure this out?
While I was able to build the site from the CLI only, in Yosemite, I switched a simple project and started a new one on Middleman and just plan to leave Cactus behind. As a Rails developer, Middleman fits better for me anyway - although if I was working with designers having the Django template language would be nice and will be missed.
@edchao try (re-)installing scss using the terminal:
sudo gem install sass
works for me with both GUI and CLI.
Boom. Thanks @pani-c worked for me!
nice! thanks @pani-c worked for me too.
Odd, I'm still having this issue and I've reinstalled sass globally. Anyone else encounter this and have a fix?
*** Rebuilding (/Users/Robert/Sites/olli-lp changed)
find /Users/Robert/Sites/olli-lp/static -name "*.scss" -not -name "_*" -exec bash -c "sassc '{}' > '{}.css'" \;
bash: sassc: command not found
I stumbled across these two comments in the plugins folder
# For scss/sass you need to install sassc: brew install sassy
run('find %s -name "*.scss" -not -name "_*" -exec bash -c "sassc \'{}\' > \'{}.css\'" \;' % pipes.quote(site.static_path))
# For coffee script you need to install coffee script: npm install -g coffee-script
# run('find %s -name "*.coffee" -exec coffee -c {} \;' % pipes.quote(site.static_path))
Ran both and solved my problem. Hooray!
Recently Ive been experiencing problems building the SASS, this is what I get in the output.
*\ Rebuilding (/Users/aaron.stezycki/Dropbox/02_Dev/Style Guide changed) find: scss: No such file or directory
My directories, settings, and all other files haven't changed yet now it fails to build correctly. Is there something I've done wrong? and has anyone else experienced this ?