tag:support.baseworks.nl,2011-05-09:/discussions/sassee/6-import-not-workingBaseworks: Discussion 2012-03-30T06:23:50Ztag:support.baseworks.nl,2011-05-09:Comment/114739012011-11-16T23:57:02Z2011-11-16T23:57:02Z@import not working<div><p>Hi Ben,</p>
<p>Not sure if this is just a typo, but you're telling it to import
'mixins', but the file is called '_mixins'? Could that be the
problem?</p>
<p>– Wouter</p></div>Wouter Vervloettag:support.baseworks.nl,2011-05-09:Comment/114739012011-11-17T00:02:21Z2011-11-17T00:02:23Z@import not working<div><p>Hi Wouter,</p>
<p>That's how I've done it in the past, and that's how it's
documented on the Sass site:<br>
<a href=
"http://sass-lang.com/tutorial.html">http://sass-lang.com/tutorial.html</a>
(at the bottom).</p>
<p>I get the same error when I use "<em>mixins" and
"</em>mixins.scss"</p></div>Ben Domanicotag:support.baseworks.nl,2011-05-09:Comment/114739012011-11-17T01:02:57Z2011-11-17T01:02:57Z@import not working<div><p>What does the {exp:sassee:file} tag look like that you are
calling in your template? I'm trying to reproduce it here, but for
me it works just fine, even @imports in @imports... it's just like
inception.</p>
<p>– Wouter</p></div>Wouter Vervloettag:support.baseworks.nl,2011-05-09:Comment/114739012011-11-17T01:11:34Z2011-11-17T01:11:35Z@import not working<div><p>{exp:sassee:file file='base-global.scss'
sass_path='/var/www/vhosts/domain.com/sites/assets/<em>/css/scss/'
css_path='/var/www/vhosts/domain.com/sites/assets/</em>/css/'
css_url='<a href=
"http://assets.appdirect.com/_/css/">http://assets.appdirect.com/_/css/</a>'
output_file='base-global-new.css'}</p>
<p>Ah, so this might throw a wrench in things. I use a different
subdomain to store my template files, css, js...</p>
<p>So my site is at /var/www/vhosts/domain.com/sites/info/<br>
But all my assets are in
/var/www/vhosts/domain.com/sites/assets/</p>
<p>Do you think it's not happy going across sites?</p>
<p>(I do this because i run a bunch of subdomains that all share
the same assets, and I wanted to keep them in one place to making
working on the site easier. It's kinda a custom MSM setup...
sorta)</p></div>Ben Domanicotag:support.baseworks.nl,2011-05-09:Comment/114739012011-11-17T01:36:36Z2011-11-17T01:36:36Z@import not working<div><p>Now you mention that is actually going "cross site" it might
have something to do with the PHP option <a href=
"http://nl2.php.net/manual/en/ini.core.php#ini.open-basedir">open_basedir</a>.</p>
<p>This basically means that PHP is not allowed to include files
that are outside of the defined paths for that domain. Could you
check if that is the problem?</p>
<p>– Wouter</p></div>Wouter Vervloettag:support.baseworks.nl,2011-05-09:Comment/114739012011-11-17T02:05:11Z2011-11-17T02:05:11Z@import not working<div><p>Ok, some more news... I've tried a few things and I've managed
to reproduce your error, but I don't think I can do anything about
it.</p>
<p>Basically, the @import's are being included relative to the main
file, but because that path isn't defined in the open_basedir
directive, it can't find the file.</p>
<p>My guess is: if you add the /assets/.. path to the open_basedir
option for all domains, it "should" work.</p>
<p>– Wouter</p></div>Wouter Vervloettag:support.baseworks.nl,2011-05-09:Comment/114739012011-11-17T06:18:09Z2011-11-17T06:18:10Z@import not working<div><p>Hi Wouter,</p>
<p>Thanks for your efforts. I'm fairly familiar with open_basedir,
I've set it up for all the subdomains on my server. Right now, all
subdomain installs of EE save their templates to a central "assets"
subdomain. Additionally, I save all uploaded content thru EE to
this "Assets" subdomain (I even host a shared EE themes folder
there). So I know that is set up properly and working.</p>
<p>I can't wrap my head around why the @import isn't working if
everything else is. Additionally, I think I would be getting a PHP
error about open_basedir if that was the cause, and I'm not, only
the error I posted above.</p>
<p>Tomorrow morning I'll test out using sassee and @import all from
within the same subdomain and just make sure I can get that to
work.</p>
<p>It feels like when the Scss is compiled, it's making an
assumption of the URL of imported scss file... Could it be based on
some "document root" variable? I know that Image CE uses a similar
variable that I believe is available thru EE. Just a thought.</p>
<p>Okay, I'll let you know how things go tomorrow, let me know if
there is anything else I can help out with or if you have any new
thoughts.</p>
<p>Best,<br>
Ben</p></div>Ben Domanicotag:support.baseworks.nl,2011-05-09:Comment/114739012011-11-17T08:26:34Z2011-11-17T08:26:34Z@import not working<div><p>The error above is one throw by the library I am using to parse
SASS. That library suppresses native PHP errors and serves up its
own instead, that is why you don't get the open_basedir error.</p>
<p>– Wouter</p></div>Wouter Vervloettag:support.baseworks.nl,2011-05-09:Comment/114739012011-11-17T15:20:39Z2011-11-17T15:20:42Z@import not working<div><p>Ah okay, do you know offhand how to let it show normal PHP
errors? I want to spend some time debugging and I think they would
help.</p></div>Ben Domanicotag:support.baseworks.nl,2011-05-09:Comment/114739012011-11-17T16:07:22Z2011-11-17T16:07:22Z@import not working<div><p>There is no easy way of turning off the Exception handling apart
from editing the library files...</p></div>Wouter Vervloettag:support.baseworks.nl,2011-05-09:Comment/114739012011-11-17T17:13:43Z2011-11-17T17:13:43Z@import not working<div><p>Hey Wouter,</p>
<p>So this morning things have mysteriously gotten worse. I can't
even get errors now (not really sure why...).</p>
<p>When I try and use an @import, I get no outputted errors, and
nothing is returned, the page is just blank.</p>
<p>Haha, I know this is probably beyond what you want to support,
especially for a free plugin, but I thought I would update.</p></div>Ben Domanicotag:support.baseworks.nl,2011-05-09:Comment/114739012011-11-17T17:26:38Z2011-11-17T17:26:38Z@import not working<div><p>Disregard my last comment, I was logged out of EE, and didn't
realize that EE suppresses ALL php errors when logged out (thought
it was just EE related errors).</p>
<p>Anyways, do you ever sleep, Wouter? (That's me saying thank you
for all the help)</p></div>Ben Domanicotag:support.baseworks.nl,2011-05-09:Comment/114739012011-11-17T17:50:32Z2011-11-17T17:50:32Z@import not working<div><p>Was about to suggest logging in, but glad to see you figured it
out.</p>
<p>I do sleep, but I have a few weeks off from my day job, so I
have a bit more time to spend on my own stuff.</p></div>Wouter Vervloettag:support.baseworks.nl,2011-05-09:Comment/114739012011-11-17T18:17:40Z2011-11-17T18:17:41Z@import not working<div><p>Alright Wouter,</p>
<p>I've tried everything I can, I can't figure it out. Thanks again
for your help, I understand that it's not really a sassee issue
(and I also know my setup is not normal).</p>
<p>It seems that although open_basedir is set up and working for
me, the sass parser isn't happy with that.</p>
<p>If you're out of ideas we can close this thread and you can get
back to enjoying you time off work :)</p></div>Ben Domanicotag:support.baseworks.nl,2011-05-09:Comment/114739012011-11-30T22:04:19Z2011-11-30T22:04:19Z@import not working<div><p>Hi Ben,</p>
<p>I've given it quite some thought and I don't think I can solve
it from my end as it is probably a server issue.</p>
<p>So if you don't mind, I'd like to close this thread.</p>
<p>– Wouter</p></div>Wouter Vervloet