Compilation of my - until recently working - scss file (under daily development for 4 weeks with no other problem) seems to be failing, with no error message provided.

A few observations:

  1. The compiled file in /sites/default/files/css/sitename_sasson.css is empty. It's called via the info file via styles[styles/sitename_sasson.scss][options][media] = all
  2. Normal CSS files called via the same .info file work fine.
  3. New .scss files, with one simple rule, also do not compile
  4. Most bizarrely, If i remove the import of one of my partials, @import "lib"; then I get errors in the message log - so some kind of attempted error checking is happening before it fails completely.

If it wasn't for item 3 in particular, I'd suspect that my s/css was to fault, but I'm really stumped as to where I should look next.

Comments

tsi’s picture

tsi commented
Status: Active » Postponed (maintainer needs more info)

If you try compiling only the new file from #3, will it still fail ?

mint5auce’s picture

mint5auce commented

Thanks for the quick response.

No, if I try only a simple test file, it compiles fine.

I guess this suggests there's something in my main file that's causing the compiler to fail .... but there are still no errors in /admin/reports/dblog. Should I be looking somewhere else?

I've also tried restarting my development VM, which didn't help. I'm also waiting for a co-developer to checkout the latest code on his isolated server and db.

tsi’s picture

tsi commented

It is not impossible that the PHP Sass compiler fails where the Ruby compiler wouldn't but you will have to go through your file and find exactly what (line? mixin? function?) is causing it.
Thanks for reporting, though.

mint5auce’s picture

mint5auce commented
Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

So, I seem to have fixed this, but I have no idea how......

I thought I'd isolated a section of nested code that was causing the problem. There were no obvious errors, but it was the newest section in the main scss file and with it removed, everything started (almost) working again.

However, I then noticed that my layout was broken. I eventually traced this to the responsive styles being set to 'Mobile First' rather than 'Desktop First' (how this had been switched, I don't know). Setting this back bought the site back as I expected to be.

BUT. It still seems there was no error in the scss, the same, unmodified file compiles fine now. Also, setting the layout back to 'Mobile First' doesn't re-break stuff.

I'll put it down to some DB/cache oddness (isn't it always?!), it feels like flicking switches just kicked the compiler back into a working state.

I must admit though, I'm still not very trusting of SASS's ability to alert me to compilation/syntax issues.

Loving it otherwise though, great work :D