Changes between Version 16 and Version 17 of NewAdminChanges

Timestamp:

Oct 30, 2005, 12:35:54 PM (19 years ago)

Author:

rjwittams

Comment:

--

NewAdminChanges

@@ -196 +196 @@
 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. 
+ * 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. 
 
@@ -215 +215 @@
 }}}
 
-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
+This works using normal template inheritance, so make sure you inherit from the right thing ( usually "admin/change_form", but for an object in an app that has its own change form, it may be "admin/<app_name>/change_form" ).  
+
+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