Opened 7 years ago

Closed 7 years ago

Last modified 4 years ago

#7893 closed (fixed)

in Admin doc, fieldsets keys are not distinct from ModelAdmin options

Reported by: anonymous Owned by: brosner
Component: Documentation Version: master
Severity: Keywords: admin
Cc: Triage Stage: Accepted
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description

In the page documentation/admin/ ,

The list of fieldset options is indistinct visually from the list of ModelAdmin options, and it is included in it.

It can be very misleading : one can understand by example that filter_horizontal is a fieldset possible key.

Solution : use another level of indentation, use a bullet point list ...

Attachments (1)

7893.admin_doc.diff (3.1 KB) - added by julien 7 years ago.
Using bullet points

Download all attachments as: .zip

Change History (7)

comment:1 Changed 7 years ago by brosner

  • milestone set to 1.0 beta
  • Needs documentation unset
  • Needs tests unset
  • Owner changed from nobody to brosner
  • Patch needs improvement unset
  • Status changed from new to assigned
  • Triage Stage changed from Unreviewed to Accepted

There actually is another level of indirection, but visually that is not be expressed very nicely.

Changed 7 years ago by julien

Using bullet points

comment:2 Changed 7 years ago by julien

Ooops, sorry brosner, I didn't realised that you were assigned to this ticket. Feel free to disregard the patch I posted ;)

comment:3 Changed 7 years ago by brosner

  • milestone changed from 1.0 beta to 1.0

comment:4 Changed 7 years ago by kratorius

  • Has patch set

comment:5 Changed 7 years ago by brosner

  • Resolution set to fixed
  • Status changed from assigned to closed

(In [8706]) Fixed #7893 -- Gave fieldsets dictionary options a better visual display to set aside from other options in the ModelAdmin due to some name clashing causing confusion.

comment:6 Changed 4 years ago by jacob

  • milestone 1.0 deleted

Milestone 1.0 deleted

Note: See TracTickets for help on using tickets.
Back to Top