Oh, sorry. I was pulling the wrong file for the Routing error. And making the whole site 777 (it's local-only so it's safe-enough) fixed the issues.
On Apr 26, 4:33 pm, Kenneth Love <[EMAIL PROTECTED]> wrote: > OK, so how should they be set up to make Apache/Rails happy? > > Running that in script/console gets it working. Obviously I don't want > to do that every time I update the stylesheets. > > Also, using the Web Developer toolbar to view the CSS (or accessing > the .css file in the browser) gives a Routing error. Is that normal? > > On Apr 26, 4:14 pm, Hampton <[EMAIL PROTECTED]> wrote: > > > I've seen this error before.... usually when the permissions for > > Apache aren't kosher with the rails directory. > > > -hampton. > > > On 4/26/07, Kenneth Love <[EMAIL PROTECTED]> wrote: > > > > Which logs would you like? > > > > development.log doesn't end with an error, it ends with a 200. The > > > error before it has nothing to do with Sass (undefined variable). > > > apache.log just says: [Thu Apr 26 15:46:50 2007] [error] [client > > > 127.0.0.1] Premature end of script headers: dispatch.cgi > > > > There isn't anything in the other log files. > > > > On Apr 26, 3:43 pm, "Nathan Weizenbaum" <[EMAIL PROTECTED]> wrote: > > > > We'll need more information. What's in the logs? > > > > > - Nathan > > > > > On 4/26/07, Kenneth Love <[EMAIL PROTECTED]> wrote: > > > > > > When I create the public/stylesheets/sass subdirectory, and put > > > > > any .sass file in it, Rails immediately crashes with the "failed to > > > > > start properly" message. Any help? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
