Changes between Version 26 and Version 27 of NewformsAdminBranch

Timestamp:

Sep 16, 2007, 1:50:39 AM (17 years ago)

Author:

jdetaeye@…

Comment:

added some info an backward incompatible changes

NewformsAdminBranch

@@ -108 +108 @@
 In this example, we register both {{{Author}}} and {{{Book}}} with the {{{AdminSite}}} instance {{{django.contrib.admin.site}}}. {{{Author}}} doesn't need any custom admin options, so we just call {{{admin.site.register(Author)}}}. {{{Book}}}, on the other hand, has some custom admin options, so we define a {{{BookOptions}}} class and pass that class as a second argument to {{{admin.site.register()}}}.
 
-(Yes, in this example, the admin options still live in the {{{models.py}}} file. But there's nothing that requires them to do so. The only requirement is that the {{{register()}}} calls are executed at some point, and putting them in the {{{models.py}}} is an easy way to ensure that. We'll likely come up with a nice convention for specifying admin options, perhaps in a file called {{{admin.py}}}.)
+In this example, the admin options still live in the {{{models.py}}} file. But there's nothing that requires them to do so. The only requirement is that the {{{register()}}} calls are executed at some point, and putting them in the {{{models.py}}} is an easy way to ensure that. We'll likely come up with a nice convention for this.[[BR]]
+A proposal convention: Specifying all admin options in a file called {{{admin.py}}}, and import it in the {{{__init.py}}} file of your application module to do the registering during the initialization.
 
 You'll notice the {{{BookOptions}}} class looks a lot like the old-style {{{class Admin}}}. Almost all of the old {{{class Admin}}} options work exactly the same, with one or two exceptions. (For the options that have changed, we've made them '''much''' more powerful.) In addition to the classic options such as {{{list_display}}} and {{{ordering}}}, the {{{ModelAdmin}}} class introduces a wealth of extra hooks you can use to customize the admin site for that particular model. For example:
@@ -195 +196 @@
 (r'^admin/doc/', include('django.contrib.admindocs.urls')),
 }}}
+
+=== Renamed 'fields' to 'fieldsets' ===
+
+'Fields' is used to order and group fields in the change form layout.[[BR]]
+It is still available in the new admin, but it accepts only a list of fields. [[BR]]
+In case one uses fieldsets to organize the fields, one needs to use 'fieldsets' instead. 
+
+An example:
+{{{
+#!python
+
+# OLD:
+class MyModelA(models.Model):
+   class Admin:
+     fields = ('field1','field2','field3','field4')
+
+class MyModelB(models.Model):
+   class Admin:
+     fields = (
+       ('group1', {'fields': ('field1','field2'),),
+       ('group2', {'fields': ('field3','field4'),),
+       )
+
+# NEW:
+class MyModelA_Options(admin.ModelAdmin):
+    fields = ('field1','field2','field3','field4')  # Renaming is optional 
+
+class MyModelB_Options(admin.ModelAdmin):
+     fieldsets = (
+       ('group1', {'fields': ('field1','field2'),),
+       ('group2', {'fields': ('field3','field4'),),
+       )