Re: [nesta] Having trouble getting sass to work with custom
templates
- From:
- Derek P. Collins
- Date:
- 2011-03-22 @ 07:31
Hi Graham,
I had not changed the CSS route, but I followed your instructions and I've
now done this, however, it still isn't automatically picking up the .scss
file and converting it to .css.
I'm not positive I have the app.rb file in the right place: I placed it
into the root directory of my project (so along with config.ru).
I'm looking at the error logs and it looks like it's looking for the the
file in the wrong place:
Errno::ENOENT: No such file or directory -
/path-to-project/mysite.com/rake/ruby/1.9.1/gems/nesta-0.9.4/views/profile.sass
And it's also looking for a .sass file even though I changed:
cache sass(params[:profile].to_sym)
to:
cache scss(params[:profile].to_sym)
What am I doing wrong?
Thanks,
Derek
On Monday, March 21, 2011 at 10:04 AM, Graham Ashton wrote:
On 20 Mar 2011, at 07:08, Derek P. Collins wrote:
>
> > I can't seem to get a custom stylesheet to work with my templates. I
created a filed named "screen.scss" in /views
>
> Did you change the CSS route so that Nesta knows to look for .scss files?
>
> I've just moved things around. I think you need the bottom of this page
(but read the whole page to make sure you know what to do with that code):
>
> http://nestacms.com/docs/design/templating-engines
>
Re: [nesta] Having trouble getting sass to work with custom templates
- From:
- Graham Ashton
- Date:
- 2011-03-22 @ 08:38
On 22 Mar 2011, at 07:31, "Derek P. Collins" <derekpcollins@gmail.com> wrote:
> What am I doing wrong?
I'm not sure. It's in the right place though. Can you post your app.rb
file and your layout?
Re: [nesta] Having trouble getting sass to work with custom
templates
- From:
- Derek P. Collins
- Date:
- 2011-03-22 @ 08:44
Sure, here they are:
app.rb: http://pastie.org/private/ewi4qrbtmtnfu6gtjyupuq
layout (which I titled profile_layout.haml as I'm using multiple layout
files): http://pastie.org/private/fvc2gfdhpmkkswuvebsqma
On Tuesday, March 22, 2011 at 1:38 AM, Graham Ashton wrote:
On 22 Mar 2011, at 07:31, "Derek P. Collins" <derekpcollins@gmail.com> wrote:
>
> > What am I doing wrong?
>
> I'm not sure. It's in the right place though. Can you post your app.rb
file and your layout?
>
Re: [nesta] Having trouble getting sass to work with custom templates
- From:
- Graham Ashton
- Date:
- 2011-03-22 @ 09:39
On 22 Mar 2011, at 08:44, "Derek P. Collins" <derekpcollins@gmail.com> wrote:
> Sure, here they are:
>
> app.rb
That's the entire app.rb — you're only supposed to be redefining routes.
I've no idea what impact that'll have.
> layout (which I titled profile_layout.haml as I'm using multiple layout files):
I wonder if it's picking up the other layout?
Any way I can look at the entire project, with sample content that is
configured to use this layout?
Re: [nesta] Having trouble getting sass to work with custom
templates
- From:
- Derek P. Collins
- Date:
- 2011-03-22 @ 18:03
Ah, I didn't realize that--the instructions on
http://nestacms.com/docs/design/templating-engines made it sound like I
needed to copy the contents of app.rb and paste into a new app.rb file for
my project. I suppose this makes more sense though ;) Just changing the
route for the CSS files and changing the method from "sass" to "scss"
fixed the problem.
Thanks for your help!
On Tuesday, March 22, 2011 at 2:39 AM, Graham Ashton wrote:
On 22 Mar 2011, at 08:44, "Derek P. Collins" <derekpcollins@gmail.com> wrote:
>
> > Sure, here they are:
> >
> > app.rb
>
> That's the entire app.rb — you're only supposed to be redefining routes.
I've no idea what impact that'll have.
>
> > layout (which I titled profile_layout.haml as I'm using multiple
layout files):
>
> I wonder if it's picking up the other layout?
>
> Any way I can look at the entire project, with sample content that is
configured to use this layout?
>
Re: [nesta] Having trouble getting sass to work with custom templates
- From:
- Graham Ashton
- Date:
- 2011-03-22 @ 18:04
On 22 Mar 2011, at 18:03, Derek P. Collins wrote:
> Just changing the route for the CSS files and changing the method from
"sass" to "scss" fixed the problem.
Awesome. :-)