Florian Lindner skreiv: > Hello, > a common problem I have is that I have references in my main template like CSS > or an background image: > > <link rel="stylesheet" type="text/css" href="styles.css" /> > > This template is used within different paths. Therefore I need to have the > styles.css availabe in every path the template could be used. > An alternative would be give the entire URL href="http://xgm.de/styles.css. > But then I need to change that line everytime when I deploy my app from > localhost to a domain. > Another working solution is to model the regexp in a way that styles.css is > always available: r"^.*styles\.css$" > It works but makes caching for browsers impossible and clutters the paths. > Is there a tag like {% domain %} that gives me the domain and I can construct > a path like http://xgm.de/styles.css dynamically (and it changes to > http://localhost:8000/styles.css when I am on localhost)? > Or how is this problem commonly solved with Django?
I solved this problem in the following way: 1) Set the stylesheet link tag to <link rel="stylesheet" type="text/ css" href="/styles.css" /> 2) Created a rule in urls.py where r"^styles\.css" points to an appropriately written view. 3) Created a view that output the desired CSS code as plain text (using a template) As far as I can see there are several advantages to this way of doing it. First, the stylesheet becomes available as http://<whateverdomainname>/styles.css, so browsers should have no problem caching it. (By the way, have a look at http://www.stefanhayden.com/blog/2006/04/03/css-caching-hack/ for a nice hack to ensure CSS caching is only done whenever you want it to be done.) Second, the full template system of Django becomes available also for generating CSS, including the nifty template inheritance feature. The view in urlconf in 2) and view in 3) could easily be modified to output different CSS files by letting the urlconf pass the name of the CSS file as a parameter to the view. Best, Håvard --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
