Hi Nathan,
Thanks for your quick reply.
I have to deep more into my application because on a brand new rails
2.0.1 application, sass works.
My Sass::Plugin.options:
$ sudo script/console production
Password:
Loading production environment (Rails 2.0.1)
>> Sass::Plugin.options
=> {:full_exception=>false, :template_location=>"/var/www/projects/
*****/releases/20071210152533/public/stylesheets/
sass", :css_location=>"/var/www/projects/*****/releases/20071210152533/
public/stylesheets", :always_update=>false, :always_check=>false}
(I hide the confidential app name with ****)
The mongrels process are owned by root and thus can write on public/
stylesheets
I guess something goes wrong in my application when I migrated over
Rails 2.0.1
Maxime
It really works on a clean brand new rails app.
On Dec 11, 12:11 am, Nathan Weizenbaum <[EMAIL PROTECTED]> wrote:
> I can't reproduce this. You are testing this in development mode, right?
> In production mode, this behavior is the default.
>
> What's Sass::Plugin.options ?
>
> - Nathan
>
> Maxime wrote:
> > Hi all,
>
> > I have to manually type:
>
> > Sass::Plugin.update_stylesheets
>
> > into script/console in order to have my CSS files out of the Sass
> > files.
> > I am using Haml trunk Revision: 687, running on Debian Etch, Ruby
> > 1.8.5, Rails 2.0.1.
>
> > Anybody got this issue as well?
>
> > Thanks,
> > Maxime
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Haml" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/haml?hl=en
-~----------~----~----~----~------~----~------~--~---
