Re: [Radiant] SnS extension problem -- Fixed (New SnS Release)

2008-07-28 Thread Marshal Linfoot
That did it! Working like a charm now. Thank you very much Chris for a great extension and for all the help getting it to work with LiteSpeed. On Mon, Jul 28, 2008 at 12:33 PM, Chris Parrish <[EMAIL PROTECTED]> wrote: > Oh, I forgot to mention, you'll need to clear the text asset cache too so > t

Re: [Radiant] SnS extension problem -- Fixed (New SnS Release)

2008-07-28 Thread Chris Parrish
Oh, I forgot to mention, you'll need to clear the text asset cache too so that the new status header gets updated. You can do this one of two ways: 1. Save a javascript or stylesheet file (this will clear the cache for all javascripts and stylesheets). 2. Delete the text asset cache

Re: [Radiant] SnS extension problem -- Fixed (New SnS Release)

2008-07-28 Thread Marshal Linfoot
Hi Chris. I hate to say it, but no change. Downloaded the latest version from the link in your message to vendor/extensions/sns. Ran the rake tasks again just to be safe. Page still displays without any styling. Here's what I see when accessing the css/elastic page directly: [EMAIL PROTECTED]> cu

Re: [Radiant] SnS extension problem -- Fixed (New SnS Release)

2008-07-27 Thread Chris Parrish
Marshal, those links helped. The controller/models weren't declaring a status code on success (just on failures) and apparently LiteSpeed doesn't like that (though Mongrel and Webrick seem just fine with it). Anyway, I've released an updated version of SnS to address this. You can get it her

Re: [Radiant] SnS extension problem

2008-07-26 Thread Marshal Linfoot
Hi Chris. I found a couple of threads in the litespeed forums that might be helpful. http://www.litespeedtech.com/support/forum/showthread.php?t=1422 http://www.litespeedtech.com/support/forum/showthread.php?t=821 -- marshal ___ Radiant mailing list P

Re: [Radiant] SnS extension problem

2008-07-25 Thread Marshal Linfoot
Thanks again Chris. I really appreciate all your help with this. I finally get what you've been saying about the 404 error. If you ask for the css file directly (http:test.octopusgardenyoga.com/css/elastic) it displays, but the response header indicates a 404 error. If you ask for it indirectly, v

Re: [Radiant] SnS extension problem

2008-07-25 Thread Chris Parrish
Marshall, I just saw this message (I use Live HTTP Headers too) as I'm preparing to leave on a two day trip. So I won't be able to do anything until I get back (didn't want you to think I was ignoring you). The big question still is: Why is LiteSpeed serving up the content fine yet assig

Re: [Radiant] SnS extension problem

2008-07-24 Thread Marshal Linfoot
LiteSpeed has a log with optional debug output but it's mostly server state information (ie. processes starting/stopping). I couldn't find anything useful. I discovered a nifty FF add-on called Live HTTP Headers, though. Here's what it shows for the production site using the old-fashioned way of i

Re: [Radiant] SnS extension problem

2008-07-24 Thread Chris Parrish
Yes, you got it right. But I need some help from other Radiant users out there. And, as I mentioned in my other email. This one's serving up with a "HTTP/1.1 200 OK" response so it looks like SnS could be the culprit. But I have *no* idea where to look in LiteSpeed to find out why it thinks

Re: [Radiant] SnS extension problem

2008-07-24 Thread Marshal Linfoot
OK Chris, I get it now. Ready for you to take a look. Thanks for all of this, by the way. Much appreciated. On Wed, Jul 23, 2008 at 7:14 PM, Chris Parrish <[EMAIL PROTECTED]> wrote: > Marshal Linfoot wrote: >> >> Chris, I hope this is what you had in mind...a slimmed down version of >> what I cur

Re: [Radiant] SnS extension problem

2008-07-23 Thread Chris Parrish
Ok, it looks like you created a page with a stylesheet template (http://test.octopusgardenyoga.com/tester) and its headers give a 200 response. So this makes me think that SnS isn't interacting well with LightSpeed (likely a bug on my part from the TextAssetResponseCache). Since I don't use L

Re: [Radiant] SnS extension problem

2008-07-23 Thread Chris Parrish
Marshal Linfoot wrote: Chris, I hope this is what you had in mind...a slimmed down version of what I currently use for the live site. Not quite. That looks like a regular html page and not a css one. To create what I was talking about, do the following: 1. Create a new template\

Re: [Radiant] SnS extension problem

2008-07-23 Thread Marshal Linfoot
Hi all. I did some more testing via CrossBrowserTesting.com and for what it's worth, both Opera and Safari on Windows XP display the styled pages. FF and IE don't. -- marshal ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiant

Re: [Radiant] SnS extension problem

2008-07-23 Thread Marshal Linfoot
Chris, I hope this is what you had in mind...a slimmed down version of what I currently use for the live site. "stylesheet" layout template with "" and a content-type of "text/css" A "styles" page that uses the "stylesheet" template, and child page "test" with slug "test.css" Simple layout templat

Re: [Radiant] SnS extension problem

2008-07-23 Thread Chris Parrish
As you mentioned, the full file is being served up but the response includes: RESPONSE: HTTP/1.1 404 Not Found That has to be the problem but what is the cause? Anybody know enough about LightSpeed to know if this is a server issue (mime-type config, perhaps)? In the meantime, can you crea

Re: [Radiant] SnS extension problem

2008-07-23 Thread Chris Parrish
Personally, I am no longer using the @import but rather building one master stylesheet via the command I mentioned earlier. This gives me the same benefits of compartmentalized code while allowing me to only serve up one file to the browser (faster download times, less bandwidth, etc.) By t

Re: [Radiant] SnS extension problem

2008-07-23 Thread Tim Gossett
On Wed, Jul 23, 2008 at 11:22 AM, Tim Gossett <[EMAIL PROTECTED]> wrote: > Since @import is not valid CSS, your browser stops processing rules, and no > styles get applied. You'll need to add a tag for every > stylesheet you want to use. > So I was dead wrong. @import is valid CSS. Sorry, folks.

Re: [Radiant] SnS extension problem

2008-07-23 Thread Josh Schairbaum
That's funny, I was just playing around with this yesterday. I'm running Radiant Edge with a recentish-SNS install. I'm using multiple imports in my stylesheets, but they have to be at the top of the file. I am not using SASS. Josh On Jul 23, 2008, at 1:47 PM, Alan wrote: Marshal Linf

Re: [Radiant] SnS extension problem

2008-07-23 Thread Alan
Marshal Linfoot wrote: More weirdness... If I point my browser (FF 3 on Linux) to http://test.octopusgardenyoga.com/css/elastic, the text of the css is displayed. But if I use that same URI, or just test.octopusgardenyoga.com, and try to validate with the W3C CSS Validator ( http://jigsaw.w3.org

Re: [Radiant] SnS extension problem

2008-07-23 Thread Marshal Linfoot
More weirdness... If I point my browser (FF 3 on Linux) to http://test.octopusgardenyoga.com/css/elastic, the text of the css is displayed. But if I use that same URI, or just test.octopusgardenyoga.com, and try to validate with the W3C CSS Validator ( http://jigsaw.w3.org/css-validator) it says "

Re: [Radiant] SnS extension problem

2008-07-23 Thread Marshal Linfoot
Weirder yet. Renders ok with Safari, but not with FF 2 on MacOSX, FF 3 on Linux, or IE 7 on Vista (last one checked with CrossBrowserTesting.com). Am I missing something obvious like needing to create a public/css directory? On Wed, Jul 23, 2008 at 11:25 AM, Chris Parrish <[EMAIL PROTECTED]> wrot

Re: [Radiant] SnS extension problem

2008-07-23 Thread Marshal Linfoot
Keith, here's the config table: mysql> select * from config; ++--++ | id | key | value | ++--++ | 1 | admin.title | Radiant CMS

Re: [Radiant] SnS extension problem

2008-07-23 Thread Marshal Linfoot
Thanks for all the quick responses! Removing the @import line fixes it for Safari, but Firefox 2.0.0.16 (MacOSX) and FF 3.0 (Ubuntu Linux) are still unstyled. Also, as Chris said if you download and run locally with FF, all's well. I'm hosting on Slicehost with the Litespeed web server. Could it

[Radiant] SnS extension problem

2008-07-23 Thread Tim Gossett
On Wed, Jul 23, 2008 at 11:25 AM, Chris Parrish < [EMAIL PROTECTED]> wrote: > My best guess is the @import line. What happens if you remove it? Removing the @import line fixes it. http://sites.google.com/a/mrgossett.com/screenshots/octopusgarden Looks good, Marshal. -- Tim __

Re: [Radiant] SnS extension problem

2008-07-23 Thread Tim Gossett
On Wed, Jul 23, 2008 at 11:31 AM, Chris Parrish < [EMAIL PROTECTED]> wrote: > Doh! Tim beat me to it. I don't have time to look right now but if those > are Sass imports, I doubt it'll work. And it doesn't look like you have a > file named: http://test.octopusgardenyoga.com/css/gallery.css > >

Re: [Radiant] SnS extension problem

2008-07-23 Thread Chris Parrish
Doh! Tim beat me to it. I don't have time to look right now but if those are Sass imports, I doubt it'll work. And it doesn't look like you have a file named: http://test.octopusgardenyoga.com/css/gallery.css You can, however, use the to include stylesheet B into stylesheet A (kind of a s

Re: [Radiant] SnS extension problem

2008-07-23 Thread Keith Bingman
On Jul 23, 2008, at 5:22 PM, Tim Gossett wrote: On Wed, Jul 23, 2008 at 11:10 AM, Marshal Linfoot <[EMAIL PROTECTED]> wrote: The Radiant production log shows: Processing SiteController#show_page (for 99.232.3.139 at 2008-07-23 14:58:33) [GET] Parameters: {"url"=>"/", "action"=>"show_page", "c

Re: [Radiant] SnS extension problem

2008-07-23 Thread Chris Parrish
Weird. Your CSS headers look right. Your CSS validates (well enough, anyway). Stranger still, if I download it using firefox and run it locally, all's well. My best guess is the @import line. What happens if you remove it? -Chris Marshal Linfoot wrote: Hi all. I'm having a problem with

Re: [Radiant] SnS extension problem

2008-07-23 Thread Tim Gossett
On Wed, Jul 23, 2008 at 11:10 AM, Marshal Linfoot <[EMAIL PROTECTED]> wrote: > > The Radiant production log shows: > > Processing SiteController#show_page (for 99.232.3.139 at 2008-07-23 > 14:58:33) [GET] > Parameters: {"url"=>"/", "action"=>"show_page", "controller"=>"site"} > Completed in 0.1928

[Radiant] SnS extension problem

2008-07-23 Thread Marshal Linfoot
Hi all. I'm having a problem with the SnS extension and need some help. Radiant 0.6.7 (gem) and Styles and Scripts extension v0.6. The extension installed without any errors, I can access the CSS and JS tabs, and have created a stylesheet called "elastic". In the layout for my pages I have: whic