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
