Adrian Holovaty wrote: > On 11/7/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > >>It's a bit of a problem for me because i want to do this. >> >>Allow users to create a Purchase Order which has several Items (of >>equipment) so item's are edited inline with purchase orders. >> >>Then for each Item needs to be edited individually including it's >>Properties which is another class edited inline with Items >> >>Is this just something djamgo doesn't do or have I defined my models >>wrong. > > > It's something Django doesn't do right now. Only one "level" of > edit_inline is supported. It's not possible for edit_inline to span > more than one level. > > However, this should be changing soon, with the new-admin code branch, > which is currently being developed. > > Adrian > Just a note : although some of the changes in new-admin are a necessary prerequisite for multilevel edit_inline, the plan was not to do it in that branch as it also involves getting rid of core fields. As the new-admin branch is still meant to be fully backwards compatible, I wasn't planning to get rid of core fields in it as this would necessitate model changes.
I think the best idea would be a relatively short lived branch, after new-admin merges, in which all of the pending model changes can be done. Then people can change their models in one hit, when this future branch is merged to trunk, rather than in dribs and drabs. For the specific case of editing an inline_edited object seperately in its own admin form, (which I believe the original poster would be satisfied with as a stop gap measure), this should already work in new-admin AFAIK. The foreign key with edit_inline=whatever is rendered as a foreign key select field like any other, ie you can select the objects "parent". Robert
