Hello, Just use RequestContext + context processor, which adds theme based context. Just use vars like base_template (which could be set to skin_basic_base.html by context processor). Hope you got the idea.
Kristaps Kūlis What this country needs is a good five cent microcomputer.<http://wertarbyte.de/gigaset-rss/?limit=140&cookies=1&lang=de&lang=en&jar_id=10394735232565416737736263810940952> On Mon, Oct 5, 2009 at 12:36 AM, ringemup <ringe...@gmail.com> wrote: > > I'd like my templates to extend different templates depending on the > skin the user has selected. The trouble is that the {% extends %} > tag has to appear in the template file before any custom filters are > loaded, so I can't run something like > > {% extends 'wrapper.html'|select_theme:user_theme %}. > > I know this can be done by selecting the template to extend in the > view and passing that as a variable to {% extends %}, but when I'm > nesting templates a couple of levels deep, it's kind of obnoxious for > my views to have to know about what other templates my templates are > calling. > > Any recommendations? > > Thanks! > > > --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
