No setter function

Mark's Avatar


23 Mar, 2012 07:39 PM

I'm getting fatal errors that all look basically like this

Uncaught exception 'SassNodeException' with message 'No setter function for parent: style.scss::15 Source: box-sizing:$type'

When I comment out the offending lines, all that changes is that SASSee finds some other line to throw exceptions about. The strange thing is that the SCSS file in question is a copy of an existing one that's in production and working fine; there are no errors. As far as I can tell all the configuration settings are the same as on my other (working) installation as well.

Is there some particular problem that tends to cause these errors if not set up properly?

  1. 1 Posted by Mark on 23 Mar, 2012 08:12 PM

    Mark's Avatar

    Actually, I've now managed to fix this problem by copying over the SASSee php files directly from the other site (as opposed to using the downloaded source files), which suggests that I must have hacked some kind of fix into place on the other site and forgot about it.

    I'd still be curious if you have any official thoughts on the error though.

  2. Support Staff 2 Posted by Wouter Vervloet on 23 Mar, 2012 08:18 PM

    Wouter Vervloet's Avatar

    Hi Mark,

    It is possible that the SASS parser I'm using is somewhat outdated, as development for it stopped just after I implemented it in Sassee. Only recently some promising replacements for Phamlp (the parser I'm using) started popping up, so I'm looking into those to keep Sassee up to date.

    Could you perhaps send a copy of the files you are using now so I can see what you've changed?

    – Wouter

  3. 3 Posted by Mark on 26 Mar, 2012 01:08 PM

    Mark's Avatar

    I just inspected the files, and it looks like the only the only change I made was to comment out the line that was throwing the exception, line 88 of SassNode.php:

    //throw new SassNodeException('No setter function for {what}', array('{what}'=>$name), $this);

    Which certainly explains why the problem went away. FWIW, I haven't had any trouble after this point, which would seem to indicate that the exception is being thrown unnecessarily in some cases.

  4. Support Staff 4 Posted by Wouter Vervloet on 26 Mar, 2012 09:22 PM

    Wouter Vervloet's Avatar

    Are you sure all your SASS is being parsed to CSS?

    Like I said, the parser I'm using at the moment is somewhat outdated, so it could be that not all current features are implemented.

    – Wouter

  5. 5 Posted by Mark on 26 Mar, 2012 09:26 PM

    Mark's Avatar

    AFAIK everything is working as expected. The only quirk I noticed is that I can't use the unitless zero, though this may be a fact about SASS itself, I've never used it before using it with SASSee. Aside from that, everything works as expected, and this is after building an entire site with it.

  6. Support Staff 6 Posted by Wouter Vervloet on 27 Mar, 2012 09:05 PM

    Wouter Vervloet's Avatar

    I'll look into it either way. Thanks for reporting the problem..

    – Wouter

  7. Wouter Vervloet closed this discussion on 27 Mar, 2012 09:05 PM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac

Recent Discussions

11 May, 2020 02:18 PM
16 Apr, 2020 06:39 AM
04 Apr, 2020 06:12 PM
30 Mar, 2020 07:50 PM
24 Mar, 2020 05:10 PM