Unfortunately, this might come from ACF, rather than Cwicly directly, as I noticed that behavior while trying to create alternative layouts depending if the repeater was used or not and had to create specific code for that.
It seems like in a Repeater, when deleting a row previously created, the ACF repeater, empty it but doesn’t delete it.
As a result, if you create a dynamic slider based on the repeater and happened to remove rows in the repeater, you will end up with empty slides in your slider.
This will happen as well with other layout than slider.
To recreate the problem,
create an ACF repeater and a repeater layout, add 3 rows to the repeater, save, check the page, go back to the repeater and delete 1 or 2 rows, save and go back to the page.
In my case I had only 1 image field as a repeater row.
I’m currently not able to reproduce this on my side.
Can you possibly set up a quick test instance on https://app.instawp.io/launch?t=cwicly&utm_source=cwicly if you have the possibility so that I can check this out when the row is removed but not completely?
I’m still seeing the 3rd row present on the backend.
I removed it and don’t have it appearing on the frontend.
Or am I misunderstanding something here?
