#8247 closed (fixed)
Incomplete documentation for AdminSite (left out step 4)
| Reported by: | Ben Davis | Owned by: | Brian Rosner |
|---|---|---|---|
| Component: | Documentation | Version: | dev |
| Severity: | Keywords: | Admin AdminSite | |
| Cc: | Triage Stage: | Accepted | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
This mentions step 4: "Instantiate your own AdminSite ..." but never mentions how to do it. The AdminSite Object section starts with hooking the AdminSite up to your urls.
Change History (3)
comment:1 by , 16 years ago
| milestone: | → 1.0 |
|---|---|
| Owner: | changed from to |
| Status: | new → assigned |
| Triage Stage: | Unreviewed → Accepted |
comment:2 by , 16 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
(In [8732]) Fixed #8247: Added explanation to admin docs to point out that AdminSite can be subclassed and instantiated like any other Python class