Applying Lightbox "Click on Expand" on 1 Image Block Automatically Adds the Option on All Other Images

[sunitarai]

I installed WordPress 6.4 Beta 3 via the Beta Tester plugin and the 2024 theme has been activated.

I went to Appearance> Editor > Templates > Blog Home and then added the "Click on Expand" option on the first image on the template.

And, when I checked the preview after saving the changes, I could see the Lightbox option had been automatically added to all the other images on the template.

[sunitarai]

Applying Lightbox "Click on Expand" on 1 Image Block Automatically Adds the Option on All Other Images

[kafleg]

Welcome @sunitarai

I'm also able to reproduce the same issue.

[digamberpradhan]

Have checked and can confirm the issue too. ​https://screenpal.com/watch/c06XDOV57HP

[hellofromTonya]

Hello @sunitarai,

Welcome to WordPress Core's Trac :) Thank you for reporting this issue.

The "Click on Expand" option and Lightbox feature is being maintained in the Gutenberg repo. Thus this issue needs to be reported upstream in Gutenberg.

Why report upstream?
WordPress Core consumes / uses the packages that Gutenberg maintains and publishes. Core itself cannot directly modify the code in those packages to address the issue you are reporting.

@sunitarai or @kafleg are you available to report this bug upstream in Gutenberg?

If yes (Thank You) and if possible, please:

• add the following labels: [Block] Image and [Type] Bug.
• and copy / paste a link to the reported issue back here in this Trac ticket for monitoring / tracking.

Until reported upstream, pulling this ticket into the 6.4 milestone for awareness and tracking.

[kafleg]

Hello @hellofromTonya

Thank you for checking. Okay, we can create that in the Gutenberg repo as well.

This ticket was created while we were running a knowledge-sharing webinar and we found this is the best place to get started for submitting the bug.

@sunitarai Can you create in the Gutenberg repo? ​https://github.com/WordPress/gutenberg/issues/new?assignees=&labels=&projects=&template=Bug_report.yml

[sunitarai]

Thank you so much @kafleg and @digamberpradhan for testing the issue.

@hellofromTonya, thank you so much for the direction. I have created the ticket on the Gutenberg repo also. Here's the link: ​https://github.com/WordPress/gutenberg/issues/55290

[oglekler]

This looks like it should be addressed on the Gutenberg side, so, I am marking this as gutenberg-merge.

[poena]

Hi
This is a duplicate of ​https://github.com/WordPress/gutenberg/pull/5519.
The problem has been solved and the fix is already planned to be included in 6.4 RC1:
​https://github.com/WordPress/gutenberg/pull/55120#issuecomment-1757410223

[digamberpradhan]

@poena I think the referred pull request is incorrect. Do you mean ​https://github.com/WordPress/gutenberg/issues/55119 ?

[hellofromTonya]

Thank you everyone.

Some history:

• The issue was initially reported in ​this Gutenberg issue.
• Was resolved, as @poena points out, in ​this Gutenberg PR.
• and the issue was included in the last week's package updates via [56849], which did ship in a silent 6.4 Beta 4.

Closing this ticket as fixed by [56849].

If the problem persists, please re-open this Trac ticket and ​this Gutenberg issue. Thank you :)