This example shows a Django admin form for an Article model. The form fields are grouped into three sections with titles and an optional description.
Django
from django.contrib import admin
from .models import Article
class ArticleAdmin(admin.ModelAdmin):
fieldsets = (
('Basic Info', {
'fields': ('title', 'author')
}),
('Content', {
'fields': ('body',),
'description': 'Write the main content here.'
}),
('Publication', {
'fields': ('status', 'publish_date')
}),
)
admin.site.register(Article, ArticleAdmin)
OutputSuccess
Important Notes
Fieldsets improve form usability and accessibility by grouping related fields.
You can add a description to explain the section to users.
Fieldsets are mainly used in Django admin forms, not in regular Django forms.
Summary
Fieldsets group form fields under a heading for clarity.
They help organize complex forms into sections.
Used mostly in Django admin to customize form layout.
Practice
(1/5)
1. What is the main purpose of using fieldsets in a Django admin form?
easy
A. To change the database schema automatically
B. To group related form fields under a common heading for better organization
C. To add validation rules to form fields
D. To create new model instances
Solution
Step 1: Understand what fieldsets do in Django admin
fieldsets are used to group form fields visually under headings to make forms easier to read and organize.
Step 2: Differentiate from other form features
Validation rules and database schema changes are handled elsewhere, not by fieldsets.
Final Answer:
To group related form fields under a common heading for better organization -> Option B
Quick Check:
Fieldsets group fields = C [OK]
Hint: Fieldsets organize fields visually, not change data or validation [OK]
Common Mistakes:
Confusing fieldsets with validation or model changes
Thinking fieldsets create new data entries
Assuming fieldsets affect database schema
2. Which of the following is the correct syntax to define fieldsets in a Django admin class?
easy
A. fieldsets = [("Section", ["name", "email"])]
B. fieldsets = {"Section": ["name", "email"]}
C. fieldsets = {"fields": ("name", "email")}
D. fieldsets = [("Section", {"fields": ("name", "email")})]
Solution
Step 1: Recall Django admin fieldsets syntax
Fieldsets must be a list of tuples, each tuple has a title string and a dictionary with a 'fields' key holding a tuple of field names.
Step 2: Check each option format
fieldsets = [("Section", {"fields": ("name", "email")})] matches the correct pattern: list of tuples with title and dict containing 'fields' tuple. Others use wrong types or missing dict.
Final Answer:
fieldsets = [("Section", {"fields": ("name", "email")})] -> Option D
Quick Check:
Fieldsets syntax = list of (title, dict with fields) [OK]
Hint: Fieldsets = list of (title, dict with 'fields' tuple) [OK]
B. The second tuple has fields as a tuple instead of a list
C. The first tuple uses a list instead of a dictionary for fields
D. Field names must be strings, not tuples
Solution
Step 1: Check the structure of each fieldset tuple
The first tuple has a title and a list of fields directly, but Django expects a dictionary with a 'fields' key.
Step 2: Confirm correct fieldsets format
Each tuple should have a dictionary with 'fields' key mapping to a list or tuple of field names. The second tuple is correct.
Final Answer:
The first tuple uses a list instead of a dictionary for fields -> Option C
Quick Check:
Fieldsets need dict with 'fields' key [OK]
Hint: Each fieldset tuple needs a dict with 'fields' key [OK]
Common Mistakes:
Using list instead of dict for fields
Confusing list and tuple types for fields
Thinking fieldsets must be dict instead of list
5. You want to create a Django admin form with three sections: 'Basic Info' (fields: name, age), 'Contact' (email, phone), and 'Preferences' (newsletter, notifications). Which fieldsets definition correctly achieves this layout?
Fieldsets must be a list of tuples, each with a title and a dictionary containing 'fields' key with a list or tuple of field names.
Step 2: Compare options for correct syntax and data types
fieldsets = [
("Basic Info", {"fields": ["name", "age"]}),
("Contact", {"fields": ["email", "phone"]}),
("Preferences", {"fields": ["newsletter", "notifications"]})
] uses list for fields inside the dict, which is valid. fieldsets = [
("Basic Info", {"fields": ("name", "age")}),
("Contact", {"fields": ("email", "phone")}),
("Preferences", {"fields": ("newsletter", "notifications")})
] uses tuple for fields, also valid but less common. fieldsets = {
"Basic Info": ["name", "age"],
"Contact": ["email", "phone"],
"Preferences": ["newsletter", "notifications"]
} uses dict with lists but keys are titles, not tuples. fieldsets = [
("Basic Info", ["name", "age"]),
("Contact", ["email", "phone"]),
("Preferences", ["newsletter", "notifications"])
] uses list instead of dict for fields.
Step 3: Choose best practice
Both A and D are valid, but Django docs often show lists for fields. fieldsets = [
("Basic Info", {"fields": ["name", "age"]}),
("Contact", {"fields": ["email", "phone"]}),
("Preferences", {"fields": ["newsletter", "notifications"]})
] matches this and is fully correct.
Final Answer:
fieldsets with list of tuples, each tuple has title and dict with 'fields' list -> Option A
Quick Check:
Fieldsets = list of (title, dict with 'fields' list) [OK]
Hint: Use list of (title, dict with 'fields' list) for clear fieldsets [OK]
Common Mistakes:
Using dict with titles as keys instead of list of tuples
Using list instead of dict for fields
Mixing tuples and lists incorrectly
Recommended
Ready to prove it?
Pass the test and this pattern moves unknownstrongwhile earning +1 Grip toward your certificate.