Re: [Radiant] SnS extension problem -- Fixed (New SnS Release)
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 here: https://secure.svnrepository.com/s_swanki/open/radiant/extensions/styles_n_scripts/tags/latest The new and improved specs now claim it's working but I don't run LiteSpeed. Could you (or somebody) test this to make sure it solves this issue? -Chris Marshal Linfoot wrote: 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 ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] SnS extension problem -- Fixed (New SnS Release)
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] curl -I test.octopusgardenyoga.com/css/elastic HTTP/1.1 404 Not Found Content-Type: text/css; charset=utf-8 Last-Modified: Wed, 23 Jul 2008 16:36:09 GMT X-Runtime: 0.00239 ETag: f95c66d251410f2f579f72e87fd28049 Date: Mon, 28 Jul 2008 13:42:16 GMT Server: LiteSpeed Connection: Keep-Alive Keep-Alive: timeout=5, max=100 PS. Minor thing...version says 0.5 on the Admin UI Extensions page. On Mon, Jul 28, 2008 at 2:15 AM, Chris Parrish [EMAIL PROTECTED] wrote: 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 here: https://secure.svnrepository.com/s_swanki/open/radiant/extensions/styles_n_scripts/tags/latest The new and improved specs now claim it's working but I don't run LiteSpeed. Could you (or somebody) test this to make sure it solves this issue? -Chris -- marshal ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] SnS extension problem -- Fixed (New SnS Release)
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 directory manually (the next request for each file will rebuild your cache). The default location for this is: [RADIANT_ROOT]/text_asset_cache. Also, I've just corrected the version issue and committed SnS v0.6.2 as the new latest version. (You can update your version of the extension but it won't affect this status header issue). Anyway, please test either version for me once you've cleared the cache and tell me if that fixes it. If it doesn't, please browse to the text asset cache directory and check the contents of the YML part of the cached file (given the default location above, it would be at: [RADIANT_ROOT]/text_asset_cache/stylesheet_cache/[your_file_name].yml). It should look something like: --- expires: 2009-07-28 10:25:57.84 -06:00 headers: Last-Modified: Thu, 19 Jun 2008 00:30:15 GMT Status: 200 OK cookie: [] Content-Type: text/css The line I care about is the Status: 200 OK one. Make sure it's there. -Chris Marshal Linfoot wrote: 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] curl -I test.octopusgardenyoga.com/css/elastic HTTP/1.1 404 Not Found Content-Type: text/css; charset=utf-8 Last-Modified: Wed, 23 Jul 2008 16:36:09 GMT X-Runtime: 0.00239 ETag: f95c66d251410f2f579f72e87fd28049 Date: Mon, 28 Jul 2008 13:42:16 GMT Server: LiteSpeed Connection: Keep-Alive Keep-Alive: timeout=5, max=100 PS. Minor thing...version says 0.5 on the Admin UI Extensions page. On Mon, Jul 28, 2008 at 2:15 AM, Chris Parrish [EMAIL PROTECTED] wrote: 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 here: https://secure.svnrepository.com/s_swanki/open/radiant/extensions/styles_n_scripts/tags/latest The new and improved specs now claim it's working but I don't run LiteSpeed. Could you (or somebody) test this to make sure it solves this issue? -Chris ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] SnS extension problem -- Fixed (New SnS Release)
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 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 directory manually (the next request for each file will rebuild your cache). The default location for this is: [RADIANT_ROOT]/text_asset_cache. Also, I've just corrected the version issue and committed SnS v0.6.2 as the new latest version. (You can update your version of the extension but it won't affect this status header issue). Anyway, please test either version for me once you've cleared the cache and tell me if that fixes it. If it doesn't, please browse to the text asset cache directory and check the contents of the YML part of the cached file (given the default location above, it would be at: [RADIANT_ROOT]/text_asset_cache/stylesheet_cache/[your_file_name].yml). It should look something like: --- expires: 2009-07-28 10:25:57.84 -06:00 headers: Last-Modified: Thu, 19 Jun 2008 00:30:15 GMT Status: 200 OK cookie: [] Content-Type: text/css The line I care about is the Status: 200 OK one. Make sure it's there. -Chris -- marshal ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] SnS extension problem
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 Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] SnS extension problem
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 assigning a 404 to the page? Again, I'm guessing that it's something with SnS but right now I don't know where to start looking. Any help by the Radiant community here would be greatly appreciated. If nobody has any suggestions, I'll start analyzing the output of the TextAssetResponseCache once I get back to see if I stumble on anything. This one smells weird. -Chris Marshal Linfoot wrote: 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 including css and for the test site using sns. The only differences I can spot are the addition of the Etag and If-None-Match headers in the test site responses. Is this significant? The html files returned are the same except for the link ... / tags. http://octopusgardenyoga.com/ GET / HTTP/1.1 Host: octopusgardenyoga.com User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9) Gecko/2008061015 Firefox/3.0 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 300 Connection: keep-alive Cookie: __utma=64320817.730990810.1201637965.1201870961.1202442307.5; __utmz=64320817.1201870961.4.2.utmcsr=octopusgardenyoga.com|utmccn=(referral)|utmcmd=referral|utmcct=%2Flists%2Fadmin%2F; style=Default; _session_id=a398654d739c03309b141883e3ae8f6c If-Modified-Since: Wed, 23 Jul 2008 16:08:48 GMT HTTP/1.x 200 OK Content-Type: text/html; charset=utf-8 Last-Modified: Fri, 25 Jul 2008 03:05:45 GMT Content-Encoding: gzip Vary: Accept-Encoding Transfer-Encoding: chunked Date: Fri, 25 Jul 2008 03:05:45 GMT Server: LiteSpeed Connection: Keep-Alive Keep-Alive: timeout=5, max=100 -- http://octopusgardenyoga.com/styles/elastic.css GET /styles/elastic.css HTTP/1.1 Host: octopusgardenyoga.com User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9) Gecko/2008061015 Firefox/3.0 Accept: text/css,*/*;q=0.1 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 300 Connection: keep-alive Referer: http://octopusgardenyoga.com/ Cookie: __utma=64320817.730990810.1201637965.1201870961.1202442307.5; __utmz=64320817.1201870961.4.2.utmcsr=octopusgardenyoga.com|utmccn=(referral)|utmcmd=referral|utmcct=%2Flists%2Fadmin%2F; style=Default; _session_id=a398654d739c03309b141883e3ae8f6c If-Modified-Since: Wed, 23 Jul 2008 16:51:31 GMT HTTP/1.x 200 OK Content-Type: text/css; charset=utf-8 Last-Modified: Fri, 25 Jul 2008 03:05:45 GMT Content-Encoding: gzip Vary: Accept-Encoding Transfer-Encoding: chunked Date: Fri, 25 Jul 2008 03:05:45 GMT Server: LiteSpeed Connection: Keep-Alive Keep-Alive: timeout=5, max=100 -- http://test.octopusgardenyoga.com/ GET / HTTP/1.1 Host: test.octopusgardenyoga.com User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9) Gecko/2008061015 Firefox/3.0 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 300 Connection: keep-alive Cookie: __utma=64320817.730990810.1201637965.1201870961.1202442307.5; __utmz=64320817.1201870961.4.2.utmcsr=octopusgardenyoga.com|utmccn=(referral)|utmcmd=referral|utmcct=%2Flists%2Fadmin%2F; _radiant_session=34d224ec40d533ed1ac0fc36474823de If-Modified-Since: Fri, 25 Jul 2008 02:24:00 GMT If-None-Match: 465d8f78af243db4736e38c4452ee778 HTTP/1.x 304 Not Modified Content-Type: text/html; charset=utf-8 Last-Modified: Fri, 25 Jul 2008 03:01:58 GMT X-Runtime: 0.20425 Etag: 465d8f78af243db4736e38c4452ee778 Date: Fri, 25 Jul 2008 03:01:58 GMT Server: LiteSpeed Connection: Keep-Alive Keep-Alive: timeout=5, max=100 -- http://test.octopusgardenyoga.com/css/elastic GET /css/elastic HTTP/1.1 Host: test.octopusgardenyoga.com User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9) Gecko/2008061015 Firefox/3.0 Accept: text/css,*/*;q=0.1 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 300 Connection: keep-alive Referer: http://test.octopusgardenyoga.com/ Cookie: __utma=64320817.730990810.1201637965.1201870961.1202442307.5;
Re: [Radiant] SnS extension problem
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 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\ * Name it: CSS * Expand the more button and change the content-type to: text/css * In the body of the layout, put nothing but: r:content * save the layout 2. Go to your tester page and change its layout to: CSS This should serve up your tester page using text/css mime type and without all the header/footer layout stuff. -Chris -- marshal ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] SnS extension problem
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 the response should be 404 -- I've never used it. Anyone? Does it have some sort of log or is there a debugging tool? TextAssetResponseCache must be handing over something different than the standard ResponseCache that pages use and LiteSpeed is choking on this difference. But I'm not getting this behavior on my development machine (which uses mongrel to serve up the content). -Chris Marshal Linfoot wrote: 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 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\ * Name it: CSS * Expand the more button and change the content-type to: text/css * In the body of the layout, put nothing but: r:content * save the layout 2. Go to your tester page and change its layout to: CSS This should serve up your tester page using text/css mime type and without all the header/footer layout stuff. -Chris ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] SnS extension problem
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 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: r:stylesheet name=elastic
as=link media=screen / which renders as link rel=stylesheet
href=/css/elastic type=text/css media=screen /. Looks okay to
me, but the page renders without the css being applied -- no styling.
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.19283 (5 reqs/sec) | DB: 0.0 (0%) | 200 OK
[http://test.octopusgardenyoga.com/]
Processing SiteController#show_page (for 99.232.3.139 at 2008-07-23
14:58:34) [GET]
Parameters: {url=[css, elastic], action=show_page,
controller=site}
Filter chain halted as
[#ActionController::Filters::ClassMethods::SymbolFilter:0x2adc426c66d0
@filter=:parse_url_for_text_a
ssets] rendered_or_redirected.
Completed in 0.01643 (60 reqs/sec) | DB: 0.0 (0%) | 304 Not
Modified [http://test.octopusgardenyoga.com/css/elastic]
I have no idea why the css isn't being applied. Tried naming it
elastic.css, same results. Tried r:stylesheet name=elastic
as=inline / and it places the css inline as expected, but no
styling.
Thanks for any help. I'm eager to use this extension for all the good
reasons Chris mentions in the README.
PS. You can see the rendered pages at http://test.octopusgardenyoga.com
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] SnS extension problem
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 r:stylesheet name=anotherfile.css to
include stylesheet B into stylesheet A (kind of a snippets for
stylesheets). That way you can skip the @import altogether. And the
extension will even track your dependencies so if B changes, its
LAST-MODIFIED will bubble up to A.
-Chris
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, controller=site}
Completed in 0.19283 (5 reqs/sec) | DB: 0.0 (0%) | 200 OK
[http://test.octopusgardenyoga.com/]
Processing SiteController#show_page (for 99.232.3.139 at 2008-07-23
14:58:34) [GET]
Parameters: {url=[css, elastic], action=show_page,
controller=site}
Filter chain halted as
[#ActionController::Filters::ClassMethods::SymbolFilter:0x2adc426c66d0
@filter=:parse_url_for_text_a
ssets] rendered_or_redirected.
Completed in 0.01643 (60 reqs/sec) | DB: 0.0 (0%) | 304 Not
Modified [http://test.octopusgardenyoga.com/css/elastic]
I have no idea why the css isn't being applied. Tried naming it
elastic.css, same results. Tried r:stylesheet name=elastic
as=inline / and it places the css inline as expected, but no
styling.
I think your problem is the first line:
@import url(gallery.css)
I don't think the SnS extension can handle SASS imports (because SASS looks
for a .sass or .css file in the filesystem, not in the DB), so it passes the
directive into the rendered stylesheet. Since @import is not valid CSS, your
browser stops processing rules, and no styles get applied. You'll need to
add a r:stylesheet / tag for every stylesheet you want to use.
Maybe Chris is working on a way to include multiple stylesheets with one
tag. For now, though, you should use one tag per css file.
--
Tim
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] SnS extension problem
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 You can, however, use the r:stylesheet name=anotherfile.css to include stylesheet B into stylesheet A (kind of a snippets for stylesheets). That way you can skip the @import altogether. And the extension will even track your dependencies so if B changes, its LAST-MODIFIED will bubble up to A. Sweet! I didn't know that. I'll start using that right away. Does the tag for the stylesheet snippet tag need inline? -- Tim ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] SnS extension problem
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 be some quirk with Litespeed? Thanks again for all the help so far. -- marshal ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] SnS extension problem
Keith, here's the config table: mysql select * from config; ++--++ | id | key | value | ++--++ | 1 | admin.title | Radiant CMS| | 2 | admin.subtitle | Publishing for Small Teams | | 3 | defaults.page.parts | body, extended | | 4 | defaults.page.status | draft | | 5 | gallery.path_prefix | public/galleries | | 6 | gallery.processor| rmagick| | 7 | gallery.gallery_based| false | | 8 | SnS.stylesheet_directory | css| | 9 | SnS.javascript_directory | js | | 10 | SnS.stylesheet_mime_type | text/css | | 11 | SnS.javascript_mime_type | text/javascript| ++--++ All's well there. On Wed, Jul 23, 2008 at 11:28 AM, Keith Bingman [EMAIL PROTECTED] wrote: The other thing you need to check is that the header is being set correctly. SnS uses a config setting in the database for this, is should be set to text/css. Strangely, the link you sent renders perfectly in Safari, though in FF it renders without css... Keith ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant -- marshal ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] SnS extension problem
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 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/css-validator) it says File not found: http://test.octopusgardenyoga.com/css/elastic: Not Found. Does this give anyone any clue as to what's going on? I am admittedly, clueless :/ On Wed, Jul 23, 2008 at 12:46 PM, Marshal Linfoot [EMAIL PROTECTED] wrote: 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? Well looking at it with FireBug on FF3 on Fedora I am seeing a 404 error for the css/elasitic file. Yet it is also returning the css content. The header does not include a content-length either. for elastic Response Headers Content-Typetext/css; charset=utf-8 Last-Modified Wed, 23 Jul 2008 16:36:09 GMT X-Runtime 0.00882 DateWed, 23 Jul 2008 17:44:53 GMT Server LiteSpeed Connection Keep-Alive Keep-Alive timeout=5, max=100 for lightbox.css Response Headers DateWed, 23 Jul 2008 17:39:46 GMT Server LiteSpeed Accept-Ranges bytes Cache-Control max-age=604800 Expires Wed, 30 Jul 2008 17:39:46 GMT Etag989-477db31c-28bd7 Last-Modified Fri, 04 Jan 2008 04:16:28 GMT Content-Typetext/css Content-Length 924 Content-Encodinggzip VaryAccept-Encoding Hope that helps... Don't really know what could be done to fix it that you haven't tried already. -- Alan Peabody ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] SnS extension problem
Personally, I am no longer using the @import but rather building one master stylesheet via the r:stylesheet 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 the way. This also works with javascript using the r:javascript tag so you could build your own custom protaculous file from the independent prototype.js, effects.js, dragdrop.js, etc. Oh, and throw in SnS Minification and it gets kinda fun. -Chris Josh Schairbaum wrote: 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 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/css-validator) it says File not found: http://test.octopusgardenyoga.com/css/elastic: Not Found. Does this give anyone any clue as to what's going on? I am admittedly, clueless :/ On Wed, Jul 23, 2008 at 12:46 PM, Marshal Linfoot [EMAIL PROTECTED] wrote: 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? Well looking at it with FireBug on FF3 on Fedora I am seeing a 404 error for the css/elasitic file. Yet it is also returning the css content. The header does not include a content-length either. for elastic Response Headers Content-Type text/css; charset=utf-8 Last-Modified Wed, 23 Jul 2008 16:36:09 GMT X-Runtime 0.00882 Date Wed, 23 Jul 2008 17:44:53 GMT Server LiteSpeed Connection Keep-Alive Keep-Alive timeout=5, max=100 for lightbox.css Response Headers Date Wed, 23 Jul 2008 17:39:46 GMT Server LiteSpeed Accept-Ranges bytes Cache-Control max-age=604800 Expires Wed, 30 Jul 2008 17:39:46 GMT Etag 989-477db31c-28bd7 Last-Modified Fri, 04 Jan 2008 04:16:28 GMT Content-Type text/css Content-Length 924 Content-Encoding gzip Vary Accept-Encoding Hope that helps... Don't really know what could be done to fix it that you haven't tried already. -- Alan Peabody ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] SnS extension problem
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 r:content 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 template called test with link href=/styles/test.css rel=stylesheet type=text/css / to use css the old-fashioned way Simple page called tester that uses the test layout template. View the rendered page at http://test.octopusgardenyoga.com/tester PS. How do you see all the HTTP response headers? On Wed, Jul 23, 2008 at 6:10 PM, Chris Parrish [EMAIL PROTECTED] wrote: 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 create a CSS page the old-fashioned way (build a template with just r:content and a content-type of text/css then create a regular old page that uses that layout)? I'd like to know what its headers look like (does it come up with a 200 like your home page or 404 like the stylesheets). That may tell us if it is server related or not. -Chris -- marshal ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] SnS extension problem
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://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] SnS extension problem
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\ * Name it: CSS * Expand the more button and change the content-type to: text/css * In the body of the layout, put nothing but: r:content * save the layout 2. Go to your tester page and change its layout to: CSS This should serve up your tester page using text/css mime type and without all the header/footer layout stuff. -Chris stylesheet layout template with r:content 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 template called test with link href=/styles/test.css rel=stylesheet type=text/css / to use css the old-fashioned way Simple page called tester that uses the test layout template. View the rendered page at http://test.octopusgardenyoga.com/tester PS. How do you see all the HTTP response headers? On Wed, Jul 23, 2008 at 6:10 PM, Chris Parrish [EMAIL PROTECTED] wrote: 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 create a CSS page the old-fashioned way (build a template with just r:content and a content-type of text/css then create a regular old page that uses that layout)? I'd like to know what its headers look like (does it come up with a 200 like your home page or 404 like the stylesheets). That may tell us if it is server related or not. -Chris ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] SnS extension problem
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 LightSpeed, does anyone else out there know a debugging procedure to identify the issue here? I'll look at my code in the meantime but there isn't much there -- it mostly inherits from Radiant's ResponseCache. -Chris ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
