#29982: Change form fields don't appear on the same as requested in
ModelAdmin.fields
-------------------------------+--------------------------------------
Reporter: Artur Ivanov | Owner: nobody
Type: Bug | Status: new
Component: contrib.admin | Version: 2.1
Severity: Normal | Resolution:
Keywords: model admin | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Old description:
> Hello. I've just updated django from 2.0 to 2.1.3 release and I have a
> problem with django admin site since.
> The problem is incorrect html view of model admin fields option.
>
> I have this code in my admin.py
>
> {{{
> @admin.register(Orders)
> class OrdersAdmin(admin.ModelAdmin):
> list_display = ('customer', 'contact_pers', 'get_email',
> 'order_number', 'order_date', 'products_list',
> 'is_add_lic', 'contractor', 'partner')
> fields = ('customer', ('order_number', 'order_date'), 'payment_day',
> 'products', 'contact_pers', 'contractor', 'is_add_lic',
> 'partner')
> }}}
>
> According to documentation fields ''order_number" and "order_date" must
> be on the same line because they're wraped in their own tuple. Вut it's
> broke since 2.1.0 release, as I guess.
>
> To demostrate what I actually have I attached a couple of screnshots
New description:
Hello. I've just updated django from 2.0 to 2.1.3 release and I have a
problem with django admin site since.
The problem is incorrect html view of model admin fields option.
I have this code in my admin.py
{{{
@admin.register(Orders)
class OrdersAdmin(admin.ModelAdmin):
fields = ('customer', ('order_number', 'order_date'), 'payment_day',
'products', 'contact_pers', 'contractor', 'is_add_lic',
'partner')
}}}
According to documentation fields ''order_number" and "order_date" must be
on the same line because they're wraped in their own tuple. Вut it's broke
since 2.1.0 release, as I guess.
To demostrate what I actually have I attached a couple of screnshots
--
Comment (by Tim Graham):
I haven't been able to reproduce this. Could you give a minimal project
that demonstrates the issue? Ideally, you could also
[https://docs.djangoproject.com/en/dev/internals/contributing/triaging-
tickets/#bisecting-a-regression bisect] to find the commit where the
behavior changed.
--
Ticket URL: <https://code.djangoproject.com/ticket/29982#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.7cf875c39df5925da4c48266d92abd77%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
