I think a decent solution here would be to for somebody to write a
helper function with the purpose of merging multiple forms in the way
people seem to expect multiple inheritance to work. It wouldn't be
part of Django proper, I imagine, but it would make a useful snippet
to pass around when peopl
On Oct 15, 7:42 am, Tobias Bender <[EMAIL PROTECTED]> wrote:
> Am I doing something wrong or is this a bug?
Hi Tobias,
You are running into a form_for_model bug[1]. SmileyChris has tried
to address this in [2], but his solution met with a little resistance
on Trac, with the final comment being
Hi.
I have tried something like that:
class MyForm(form_for_model(Model_A), form_for_model(Model_B)):
...
myform = MyForm()
but the resulting myform.as_table() contains the fields which are from
form_for_model(Model_A) only. When changing the class MyForm to class
MyForm(form_for_model(Mode
I saw this changeset go in and am wondering if it is possible to
specify a sequence order for the fields to display. Example:
class Person(Form):
first_name = CharField()
last_name = CharField()
class PersonWithMiddle(Person):
middle_name = CharField()
But where
