Compass CSS build error #241

Closed
mh00h opened this Issue May 5, 2013 · 5 comments

Comments

2 participants
@mh00h

mh00h commented May 5, 2013

After running python manage.py collect static, I cd to /var/www/static/zinnia and ran compass compile but receive the following error:

    error sass/screen.scss (Line 27 of sass/partials/_layouts.scss: Mixin container takes 0 arguments but 2 were passed.)

After this, no CSS will be served by the server, but the image below appears on the site. Does anybody know how to fix this?

selection_001

@Fantomas42

This comment has been minimized.

Show comment Hide comment
@Fantomas42

Fantomas42 May 6, 2013

Owner

Hi,

why do you ran compass compile after the collect static process ? It's not really logic...

About the Sass error, this is certainly related to version of the gems used.
Take a look at http://docs.django-blog-zinnia.com/en/latest/how-to/customize_look_and_feel.html#compass-and-sass for having more informations about the versions used.

Owner

Fantomas42 commented May 6, 2013

Hi,

why do you ran compass compile after the collect static process ? It's not really logic...

About the Sass error, this is certainly related to version of the gems used.
Take a look at http://docs.django-blog-zinnia.com/en/latest/how-to/customize_look_and_feel.html#compass-and-sass for having more informations about the versions used.

@Fantomas42 Fantomas42 closed this May 6, 2013

@mh00h

This comment has been minimized.

Show comment Hide comment
@mh00h

mh00h May 6, 2013

I am very new to this. My understanding is that you runmanage.py collectstatic to create a template directory that can then be further edited, preserving (and overriding) zinnia's system default css in the /usr path. Then, .scss files can be edited in /var/www/stat/c/zinnia/ and recompiled using compass.

It also appears my gems are are up-to-date:

$gem list
chunky_png (1.2.8)
compass (0.12.2)
compass-susy-plugin (0.9)
compass-validator (3.0.1)
fssm (0.2.10)
sass (3.2.8)
stitch (0.1.6)
susy (1.0.8)

mh00h commented May 6, 2013

I am very new to this. My understanding is that you runmanage.py collectstatic to create a template directory that can then be further edited, preserving (and overriding) zinnia's system default css in the /usr path. Then, .scss files can be edited in /var/www/stat/c/zinnia/ and recompiled using compass.

It also appears my gems are are up-to-date:

$gem list
chunky_png (1.2.8)
compass (0.12.2)
compass-susy-plugin (0.9)
compass-validator (3.0.1)
fssm (0.2.10)
sass (3.2.8)
stitch (0.1.6)
susy (1.0.8)
@mh00h

This comment has been minimized.

Show comment Hide comment
@mh00h

mh00h May 12, 2013

I reverted to the previous gems and continue to get these errors. After discussing this topic at http://stackoverflow.com/questions/16449160/mixin-container-takes-0-arguments-but-2-were-passed/16503076?noredirect=1#16503076, our best guess is that there is either a missing file or that mixin just shouldn't be getting passed the two variables that it is currently getting. However, even when editing those variables out, compass still refuses to compile. I think there's something to this error that goes beyond the container mixin.

mh00h commented May 12, 2013

I reverted to the previous gems and continue to get these errors. After discussing this topic at http://stackoverflow.com/questions/16449160/mixin-container-takes-0-arguments-but-2-were-passed/16503076?noredirect=1#16503076, our best guess is that there is either a missing file or that mixin just shouldn't be getting passed the two variables that it is currently getting. However, even when editing those variables out, compass still refuses to compile. I think there's something to this error that goes beyond the container mixin.

@mh00h

This comment has been minimized.

Show comment Hide comment
@mh00h

mh00h May 31, 2013

I got this fixed by uninstalling the depreciated gem compass-susy-plugin.

mh00h commented May 31, 2013

I got this fixed by uninstalling the depreciated gem compass-susy-plugin.

@Fantomas42

This comment has been minimized.

Show comment Hide comment
@Fantomas42

Fantomas42 May 31, 2013

Owner

Ok I see.
Glad that you have found the solution.

Owner

Fantomas42 commented May 31, 2013

Ok I see.
Glad that you have found the solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment