[Escalated to 2nd Tier] Separate the image gallery for each child CPT displayed within a parent post

[Author]

Posts

[justinB-3]

Tell us what you are trying to do?
Separate the image gallery for each “progress update” which is a child CPT of “in production”
This is an example of “in production” post - hidden link

Instead this is happening, link to a screen recoding - hidden link

Is there any documentation that you are following?
https://toolset.com/course-lesson/dynamic-galleries-and-sliders-for-templates-displaying-repeating-image-fields/
but I think this is a little different because the repeating images are from a child.

Is there a similar example that we can see?
This is what we’re trying to recreate: hidden link
Each gallery update should be separate from the other

What is the link to your site?
hidden link

[Nigel]

Hi Justin

I ran some tests locally, and I see that when multiple galleries are output on a page coming from a View, the lightboxes pollute each other.

Rather than each gallery having a lightbox limited to that gallery's images, all images on the page are included in each lightbox.

We fixed this previously for image sliders, but it seems this is the first time it came up with galleries.

Having confirmed the problem I have escalated it to the developers, and I'll get back to you when I have any feedback to share.

[justinB-3]

Hi Nigel,

Any update on this issue?

Thanks

[Nigel]

Sorry Justin, no, I checked the internal ticket and I don't see any updates.

It is on the development board, but hasn't been handled yet.

I've commented on the internal ticket that you are asking about progress, but I can't say when a developer will pick it from the board to work on.

[justinB-3]

I understand. Can you at least point which files in Toolset this function can be found? Maybe we can have a look and just add a custom code to resolve the issue on our end for now?

Thanks

[Nigel]

I can't, I'm afraid.

When escalating an issue such as this I first try to identify the code responsible to see if I might be able to produce a workaround myself while waiting on the devs. At the time I couldn't locate the code which generates this output. I looked again yesterday when you prompted me, and I've just gone through it again.

It is more complicated in this blocks-era. The relevant code is written in React and goes through a lengthy build process which renders it unrecognisable when it comes to the code that actually ships with the plugin and is therefore accessible to you (or I). It's not like the good old days where it was just a question of identifying the responsible PHP code and making some tweaks to the source.

I'm afraid there is no alternative but to wait for the devs to work on this.