tickets: 8299
This data as json
| id | created | changetime | last_pulled_from_trac | stage | status | component | type | severity | version | resolution | summary | description | owner | reporter | keywords | easy | has_patch | needs_better_patch | needs_tests | needs_docs | ui_ux |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 8299 | 2008-08-13 23:00:18 | 2011-09-28 16:12:17 | 2022-03-06 03:41:53.115221 | Accepted | closed | Documentation | dev | fixed | Docs on ModelAdmin.form attribute need improvement | At the moment it is not really clear from the docs that you have to supply a subclass that already has a Meta class in it. From reading it I thought this would be added by the admin (as happens if you don't set the form attribute). This interpretation is also enforced by the lack of a Meta class in the validation example given later on. The attached patch fixes the example and tries to be a bit more explicit in the form attribute explanation. | nobody | jarrow | 0 | 1 | 0 | 0 | 0 | 0 |