No update when using nested inline generic foreign keys about django-super-inlines HOT 2 OPEN

Hi Again Bertrand,

A quick update. During further testing, this seems a general property of a 4-level nested inline, rather than being the result of a GFK. If I can pinpoint the problem and develop a solution, I will post the solution here.

george.

from django-super-inlines.

I just ran in to this problem as well, it has to do with the naming of the input fields in the inline admins. These are always referencing the first inline, for example, I have a product database with quite an extensive tree-like datastructure and in all of the 4th-level inlines, the names are similar to this:

prdcts-product_languages-0-0-ean
prdcts-product_languages-0-1-ean
(For the first product version)

For the inline for second product version, I would expect:

prdcts-product_languages-1-0-ean
prdcts-product_languages-1-1-ean

But they are identical to the names from the first one.

So, multiple inlines for the same product 'version' work, but if you have multiple higher level records in the tree, the 4th level records always point to the first one.

from django-super-inlines.