[Django] #28994: Create possibility to merge several fields into one line with fieldset option

10 views
Skip to first unread message

Django

unread,
Jan 7, 2018, 3:23:57 PM1/7/18
to django-...@googlegroups.com
#28994: Create possibility to merge several fields into one line with fieldset
option
-------------------------------------------+------------------------------
Reporter: Rovshan Musayev | Owner: nobody
Type: New feature | Status: new
Component: contrib.admin | Version: 2.0
Severity: Normal | Keywords: django-admin
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------------+------------------------------
Currently with **fields** or **fieldsets** option it's possible to show
admin fields into one line,

fields=(('Field1','Field2'), ('Field3','Field4'))

Field1 | Field2
Field3 | Field4

But if I would like to merge Field 2 and Field 4 into one field and have
one big field, it's impossible.

Field1 |
Field2 | Field4
Field3 |

Field4 is one big field here

It's very useful for example if I want to show one big picture(avatar) on
the right(or left) side of the form. I hope it's clear what I mean

--
Ticket URL: <https://code.djangoproject.com/ticket/28994>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

Django

unread,
Jan 8, 2018, 10:23:44 AM1/8/18
to django-...@googlegroups.com
#28994: Create possibility to merge several fields into one line with fieldset
option
---------------------------------+--------------------------------------

Reporter: Rovshan Musayev | Owner: nobody
Type: New feature | Status: new
Component: contrib.admin | Version: 2.0
Severity: Normal | Resolution:

Keywords: django-admin | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+--------------------------------------

Comment (by Tim Graham):

No, I'm not sure what you mean. Specifically, 'merge Field 2 and Field 4
into one field and have one big field" is unclear. Maybe if you provided a
sample project that would help clarify.

--
Ticket URL: <https://code.djangoproject.com/ticket/28994#comment:1>

Django

unread,
Jan 9, 2018, 9:51:58 AM1/9/18
to django-...@googlegroups.com
#28994: Create possibility to merge several fields into one line with fieldset
option
---------------------------------+--------------------------------------

Reporter: Rovshan Musayev | Owner: nobody
Type: New feature | Status: new
Component: contrib.admin | Version: 2.0
Severity: Normal | Resolution:

Keywords: django-admin | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+--------------------------------------

Comment (by Rovshan Musayev):

For example, to reorganize fields like in the picture:
[[Image(https://cdn.discourse.org/sitepoint/uploads/default/21471/b96216ac5f87b80c.png)]].
Is it only way currently to override change_form.html and fieldset.html ?

--
Ticket URL: <https://code.djangoproject.com/ticket/28994#comment:2>

Django

unread,
Jan 9, 2018, 10:48:52 AM1/9/18
to django-...@googlegroups.com
#28994: Create possibility to merge several fields into one line with fieldset
option
---------------------------------+--------------------------------------

Reporter: Rovshan Musayev | Owner: nobody
Type: New feature | Status: closed
Component: contrib.admin | Version: 2.0
Severity: Normal | Resolution: wontfix

Keywords: django-admin | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+--------------------------------------
Changes (by Tim Graham):

* status: new => closed
* resolution: => wontfix


Comment:

Yes, I think complex form layouts like that are outside the scope of the
admin.

--
Ticket URL: <https://code.djangoproject.com/ticket/28994#comment:3>

Reply all
Reply to author
Forward
0 new messages