I looked at your solution page and it seemed a bit more complicated than necessary.
Couldn't you just set up your skin to have something like: <link rel='stylesheet' href='http://mysite/myfield/pages/$$css' type='text/css' /> The $$css variable will check for values in the following order: * A system var named css * A page data var named css * A var on code.skinvars Meaning you could set a default page on code.skinvars, and then override it on any page by setting data field css to a different page. Or you could combine it with config manipulation if you wanted something more fancy. We could also get this to work hierarchically--which would be a really nice trick and make it easy to do things like metatags, etc. I'll make a note to look into this. Your .htaccess trick of course is still necessary (unless you create a new css folder--but then the css files aren't easily editable). Am I missing something? Cheers, Dan --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "BoltWire" 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/boltwire?hl=en -~----------~----~----~----~------~----~------~--~---
