Thanks Mathew,
I do have multiple forms, and that is why the nested loop.
I'm going to try to upgrade to the latest 1.10 and see if it solves the
problem. If anything I will be able to use the field_order attribute.
I reverted to a commit before I upgraded from 1.5 to 1.8 and the problem
was not present, so I suspect the upgrade changed some related behavior.
Maybe it was that change in ver. 1.7 as you suggested.
On Monday, January 9, 2017 at 9:19:34 AM UTC-8, Justin J wrote:
>
> I have a form which is sublassing 3 forms, and has no new fields.
>
> class D(A, B, C):
> pass
>
>
> form class B is subclassing 2 forms.
>
> class B(B1, B2):
> pass
>
>
>
> In the template I am looping through the form.
>
> {% for d in forms.myforms %}
> {% for field in d.form.visible_fields %}
>
> {% endfor %}
> {% endfor %}
>
>
>
> This was working as expected until recently. Form classes A, B, C are
> displayed in reverse order now, and B1, B2 are also reversed. However,
> fields within B2 are still in the order declared.
>
> The only thing I can think of that changed recently was an upgrade from
> Django 1.5 to 1.8. I have no clue if it is related.
>
> Anyone experience this before?
>
> Thanks for any suggestions.
>
>
>
>
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/be3f676d-317c-498b-834e-a048aa5ee341%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
