• Resolved TrishaM

    (@trisham)


    We recently moved a website from an Apache server to an NGINX server (IONOS to Kinsta) and as part of that process had to update the core WP to 5.8. At the same time, our Easy FancyBox plugin stopped working – all looks fine in the settings, but images no longer open in an overlay, nothing at all happens when they’re clicked on.

    It was working fine before the site move and before updating WP core.

    In doing some reading I found several posts elsewhere that hinted that the problem might be with WP’s core “lazy loading” of images, but I’m wondering if that’s the actual problem? Is there any difference in an NGINX server that might also be causing a problem? I’m frustrated with several other issues with Kinsta hosting, enough that I’m considering move the site back to IONOS, but either way I’d like to get this FancyBox plugin problem fixed.

    We don’t really need the lazy loading of images, I’d rather have FancyBox working, but I don’t know how to disable that, there doesn’t appear to be a core Setting that enables/disables the lazy loading.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Hi Trisha, no the plugin has been tested both on WP 5.8 and Nginx. Is it possible to share a link so I can see it failing live?

    If not, can you check if the fancybox scripts and snippets are in the page source? You can open a page source usually with Ctrl+U. Scroll down to the footer or use Ctrl+F to search for “fancybox”.

    Next step would be to reload a page with the Developer Toolbar open (usually F12, then F5) and see if there are any big script errors mentioned in the Console tab…

    Thread Starter TrishaM

    (@trisham)

    Hello @ravanh (Rolf) – my apologies, I discovered late yesterday that the problem is NOT with the plugin, I planned to come back here this morning to post an update but I deeply appreciate your quick response and offer to help.

    The problem was user error – I have a few new writers who apparently were not properly trained on adding images, so it was entirely our own fault, not the plugin.

    All is working great now that we figured it out, it’s still one of the best plugins we use….I’m sure I’ve given it a 5-star review in the past, but I’ll double check that to be sure, it’s definitely 5-star-worthy.

    I’ll mark this ‘resolved’. ??

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Conflict with LazyLoad?’ is closed to new replies.