Changes between Version 15 and Version 16 of NewAdminChanges

Timestamp:

Oct 30, 2005, 11:52:13 AM (19 years ago)

Author:

rjwittams

Comment:

--

NewAdminChanges

@@ -192 +192 @@
 == Admin converted to separate templates ==
 
-The admin is now rendered using separate templates. These can be overloaded, meaning the admin is a bit easily customizable. 
-Inline editing can use a custom template, reather than using edit_inline=meta.TABULAR or meta.SOURCE, just use a path to a template, eg edit_inline="edit_inline_horizontal".
-
- This does require knowing the contents of the context for that template which is undocumented. Also this will probably change to a class to allow more flexibility, eg processing for style/grouping logic etc. 
+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. 
+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:
+{{{
+
+{%extends "admin/change_form" %}
+
+{% block branding %} Customised title {% endblock %}
+{% block after_field_sets %} Some interesting information after the field sets  {% endblock %}
+
+}}}
+
+This works using normal template inheritance, so make sure you inherit from the right thing. 
+
+In the change forms, the following blocks are available for custom overriding:
+
+branding - included from "admin/base"
+form_top - at the top of the form after the title. 
+after_field_sets - after standard field sets, before the related objects
+after_related_objects - after edit_inline objects
+
+
+Inline editing can be customised. rather than using edit_inline=meta.TABULAR or meta.SOURCE, you can define a custom inline editing mode. This is done by subclassing BoundRelatedObject, and using that class. eg edit_inline=HorizontalScroller.