Compatibility with Nova Dependency Container

[dividy]

Hello,

Anybody else having issues with Nova Dependency Container inside Flexible Content ? I'm using a custom Preset & Resolver. Data is saved correctly in the DB.

If I add 2 products to my "product" layout, the 1st product's fields have the last product's values. (eg. in DB: sale_price: 3/sale_price:1 gives sale_price:1/sale_price:1 in the edit form...)

Any idea ?

[toonvandenbos]

Hi @dividy,

Is your issue similar to #129 ?

[deckchan]

No, this is not similar to 129.

Confirm this is still happening in:

• laravel/nova v3.6.0
• epartment/nova-dependency-container 1.2.11
• whitecube/nova-flexible-content v0.2.5

I checked this should be a data displaying issue.

In Update Form

all flexible elements' values are replaced by the last flexible element value if using NovaDependencyContainer

[phrasetagg]

Hello! Is it possible to solve this problem? And i can't fiind an issue wich is duplicated by this one @Nyratas

[toonvandenbos]

Hi @phrasetagg, thanks for the feedback. I'm hoping to find some time for these urgent issues soon.

[Blindmikey]

This seems to be due to duplicate field IDs - caused by the flexible "key" not being appended to the field ID for all fields in a NovaDependencyContainer that's housed in a Flexible.

[Blindmikey]

Trying to narrow down the issue, it looks like renameFields() isn't being fired for fields inside of NovaDependencyContainer fields.

[Blindmikey]

Solved my issue by using a custom class extending layout and using duplicateAndHydrate()

[MorningAM]

Solved my issue by using a custom class extending layout and using duplicateAndHydrate()

Can you please share your solution?

[daanadriaan]

There's a workaround mentioned in this issue