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
