Image not working on nested flexible content about nova-flexible-content

[jackabox]

Seems to have fixed everything up - many thanks! :)

[emilaspman]

Confirmed. I can now update other fields without images disappearing.

Thanks for this amazing plugin!

[voidgraphics]

Are you getting an error message? Image fields seem to work fine when we use them.

Maybe take a look here.

[jackabox]

Normal images are fine, I'm referring to when they are nested. I have a Flexbile field inside a Flexbile field and the image upload here does not process the image.

No error is shown or logged.

[voidgraphics]

Thanks for the clarification, we will look into it asap.

[drobee]

Do you have any workaround to this? I'm trying to create a gallery field where all the images are nested image fields.

[casberkman1]

I have the same problem

[jackabox]

@drobee no workaround that I know yet. Hoping @voidgraphics or team can get an update for this as the package is awesome otherwise.

[voidgraphics]

@jackabox I will do my best to take a look at this today and hopefully have a fix for you guys.

Thanks for the kind words!

[toonvandenbos]

Good news!

We just sat together with @voidgraphics in order to close this issue. It is shipped in the latest release (v0.1.3). Can you confirm it fixes your use cases? Thank you!

[emilaspman]

I updated to 0.1.3 and now image upload works for nested flexible content. But if I update another field after uploading and saving images, they disappear.

[toonvandenbos]

Hi @emilaspman,

Good point. I will check this right away.

[toonvandenbos]

Should be solved in the latest release (v0.1.4). Can you confirm?

Thank you!

[Sauruz]

Should be solved in the latest release (v0.1.4). Can you confirm?

Thank you!

It seems that in the latest version (1.0.7) a problem with the images has returned. Or at least, Images do not display after uploading and I'm not able to delete them. After clicking the removal icon, the popup appears. After confirming nothing happens.

[dimon-camelot]

The same problem v1.0.12

[tmartty]

I can confirm the problem has returned with v1.0.12

Any workaround or possible fix?