I have read the following page

http://code.djangoproject.com/wiki/NewAdminChanges

and it states ...

Admin converted to separate templates ΒΆ

The admin is now rendered using separate templates. These can be
overloaded, meaning the admin is a bit more easily customizable.

An example is change forms - these are the forms used to modify and add
objects in the admin. The templates are selected in the following order
:

    * admin/<app_label>/<object_name>/change_form
    * admin/<app_label>/change_form
    * admin/change_form

So it is possible to change the form just for one kind of object, or
for one app. This makes it possible to add in extra information or
change existing blocks eg branding.

So if we take the polls app as an example, we may want to customise the
admin page just for the polls object.

We create a file admin/polls/polls/change_form.html in our apps
template directory, with the contents:


So, I have a person object in my model in my so I created a test
template with the following text ...

{%extends 'admin/change_form' %}

{% block branding %} Customised title {% endblock %}
{% block after_field_sets %} Some interesting information after the
field sets  {% endblock %}

and saved it in the file
/templates/admin/wagdogs/person/change_form.html

My problem is that when I add or edit a person I do not see anything.

I would greatly appreciate it if someone could help me figure out why
this template is not being used.

Thanks,
Jim Fritchman


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