> It's really impossible to speculate given the information provided. Not really-- I mean, the *original* post was pointless, but the followup does give people who want to help something to go on.
My guess is that the template is including the CSS as a *RELATIVE* URL (as opposed to an *ABSOLUTE* URL). Well, surprise surprise, if the browser is viewing "/students/blah.html" and the document references "css/mystyles.css", it's going to ask for "/students/css/ mystyles.css", which is a different location than it'd look if the browser was viewing a root-directory file like "/home.html". I'd bet $1 that it'll work if you modify the template for that page with a "../" in front of your CSS reference. That may not be possible/ practical if you're inheriting from a base template, though, so the best bet for a REAL fix is to simply specify an *ABSOLUTE* URL for the CSS; then the URL of the document itself will be irrelevant. <link rel="stylesheet" href="/media/css/mystyles.css" /> <!-- note that it begins with a SLASH, in case you're new to the "relative vs absolute" terminology --> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
