Bug with nested flexible content fields

[arnespremberg]

If I have a flexible content field sitting within an ACF flexible content layout, hiding the first two layouts of the parent flexible content field will also hide the first two layouts within the nested flexible content field.

Please excuse the short bug report, I currently don't have time to go into more detail, but will follow suit with steps to reproduce and a screen recording.

[patel2002sag]

Hi, I am experiencing a similar problem with nested layouts. Let's consider the Accordion Component as an example. Within this component, there are two sections, and each section contains two layouts. If I were to disable the first layout within the first section, it would appear as disabled when clicking on the eye icon. However, when I update the page to render the changes on the front-end, the first layout in the second section also appears as disabled in the backend.

When inspecting the layouts in the Chrome DevTools, I observed that when the eye icon is clicked, the "acf-layout-hidden" class is added to the layout's div container. However, when updating the page, that same class gets added to the parallel row of the second container causing the layout to disable in the back-end.

1. Here I am disabling the first layout within the first section

2. Then I am updating the page to display it within on the front end

3. Finally upon updating the page notice how the first layout within the second section also gets disabled

Hope that was clear on what the exact problem is, there is a small bug where disabling the first layout within a specific section causes the parallel layout in the second section to also disable in the back-end.