Andy Dustman wrote:

You need to provide your own replacement for some admin templates,
specifically admin/base_site.html and maybe admin/base.html, depending
on what you want do do, and put them in one of your TEMPLATE_DIRS.

For i18n purposes it would be neat if you could do it in the model
definition e.g. for a class called Blog_entry you could in its Meta
class have a classname variable or similar, so the class name that
shows up in he admin may be non-ascii. That would lessen the need to
deal with templates...just my opinion.


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to