Changes between Version 38 and Version 39 of NewformsAdminBranch

Timestamp:

Nov 11, 2007, 8:34:50 AM (17 years ago)

Author:

Karen Tracey <kmtracey@…>

Comment:

--

NewformsAdminBranch

@@ -204 +204 @@
 You have to add this line before {{{r'^admin(.*)'}}} otherwise it won't work.
 
-=== Renamed 'fields' to 'fieldsets' ===
+=== Renamed 'fields' to 'fieldsets', and changed type of 'classes' value ===
 
 '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. 
+In case one uses fieldsets to organize the fields, one needs to use 'fieldsets' instead. [[BR]]
+Also, if 'classes' is specified in a field specification, then the type of its value needs to be changed from a string to a tuple of strings when migrating to the new 'fieldsets' specification.
 
 An example:
@@ -222 +223 @@
    class Admin:
      fields = (
-       ('group1', {'fields': ('field1','field2')}),
-       ('group2', {'fields': ('field3','field4')}),
+       ('group1', {'fields': ('field1','field2'), 'classes': 'collapse'}),
+       ('group2', {'fields': ('field3','field4'), 'classes': 'collapse wide'}),
        )
 
@@ -232 +233 @@
 class MyModelB_Options(admin.ModelAdmin):
      fieldsets = (
-       ('group1', {'fields': ('field1','field2')}),
-       ('group2', {'fields': ('field3','field4')}),
+       ('group1', {'fields': ('field1','field2'), 'classes': ('collapse',)}),
+       ('group2', {'fields': ('field3','field4'), 'classes': ('collapse', 'wide')}),
        )
 }}}