Unable to disable Fancybox with Additional Class

Hi and thanks for the report. I just went to test this and I was able to duplicate it for at least one configuration for image/gallery blocks. I’d like to be sure if I fix this issue, I fix it completely for you.

Is there any chance you can provide a link to a page where this is happening so I can see the mark up?

If not, can you tell me how you are adding the images? Is it via the block editor, with an image or gallery? Or via some other mechanism?

Thanks.

FirelightWP,

Thank you for responding. I have begun to had this issue on several websites. Here is an example: https://majesticviewsfloats.com/fishing-tours/ . The fish logo on that page was originally uploaded through the media manager. Placed on the page through an image block and retrieved through the media manger. When first brought in to the page it does have the chain link highlighted. Normally you would simply unlink the image but even after unlinking it, saving and clearing the cache the image will still expand on hover and click. I then added the css class “nolightbox” and “nofancybox” to the “Additional CC Class” section of WordPress, saved, cleared the cache and it still continues to expand on hover and enlarge of click. I hope this gives you enough detail.

Thank you again for looking into this.

FirelightWP,

One more thing. I may be wrong but it appears that the problem is only on images inserted after the last update. I have gone to sites that we have built that had images that were previously set to not use FancyBox but now they have links and were expanding on click. I unlinked them and they no longer are expanding, however as a test I added a new image to this same site and this new image did not have a chain link highlight but it was still expanding on click. I even tried linking and then unlinking the image but this still did not disengage Fancybox.

Hi – thanks for the link and all the extra supporting information. That’s great. I’ll dig into this later today and will include a fix in the next release. That will probably go out early next week.

Hi, I did track down the issue and resolve it today. It’s pushed to the code base and will go out with the next release. Just to keep the forums tidy, I’m going to make this as resolved for now, but if you still have any related issues at all when you update, please definitely follow up here.

FirelightWP,

Thank you so much for following up on this and for getting to it so quickly. It always puts my mind at ease to use a plugin from an author who really seems to care.

Thanks.