Firelight

Just wanted to follow up and let you know we’ve released this change. Again, for the translations to show, translations for the new strings will need to be added via the WordPress translation system (ie, at https://translate.wordpress.org/locale/ru/default/wp-plugins/easy-fancybox/)

Hi @michaelxxx –

Sorry for the delayed response. I don’t *think* anything changed that would affect or produce the behavior you are describing, at least not recently – but it’s always possible.

I just checked the link to see the behavior. Have you resolved this? From what I can tell, it seems to be working – by which I mean none of the gallery images seems to be opening in our lightbox, but rather in JIG’s as it sounds like you’d expect.

If I’m mistaken, let me know and I’ll have a look.

I wanted to let you know I’ve updated the code to add translatable strings for these button tooltips. It will go out in the next release. Once released, keep in mind the strings will need to be actually translated into Russian at https://translate.wordpress.org/locale/ru/default/wp-plugins/easy-fancybox/ before the Russian translations will show.

Since I’ve fixed the issue in the code (even if not released yet), I’m going to mark the issue resolved. But if you still have issues once the next release is out, please do not hesitate to follow up.

Yes, I just looked at this. The tooltips that appear on mouseover are provided by the Fancybox scripts, and are hard coded into the JavaScript. To make them translated, we’d need to pass translatable strings to Fancybox, and update the Fancybox scripts to use those. Once that’s in place, we’d also need those strings to be translated of course.

This seems manageable, and I’ll put it on our dev agenda. I’m not quite sure when we’ll get to it, but will follow up here when we do.

You have the right idea! You can add an image to the classic editor like normal, and set it to link to media file, and it will open in the lightobx. And it is working on your site – the image is opening in the lightbox.

But I do also see the ‘double lightbox’ problem on your site. One of them is fancybox – from our plugin. The other (I think) is magnific popup. That’s not from our plugin, though. It’s likely it is being provided as a lightbox either by the theme, or by another gallery / lightbox plugin. You’ll need to figure out what is providing that, and disable it. Whether it is a theme or plugin, it almost certainly has a setting to disable the lightbox.

Hi thanks for the review! You’ll be happy to know that we have no plans or intent to remove the Fancybox Legacy lightbox. 🙂

It’s worth noting the ‘legacy’ version (1.3.28) was released in July 2011 – 14 years argo. It’s amazing that it continues to work. But given its age, there may come a point where it just starts breaking in ways that aren’t easy to fix. If it ever gets removed, it would be for that reason.

Given it is there and working, with no intent to remove, it would great if you could bump to 5.0. If we ever remove it, you can bump us back down, and we’ll understand. 🙂

Apart from all that, it’s good of you to come here and post about it. Hearing that people still use and appreciate will encourage us to to keep it and continue fixing issues as they arise.

@intowernet – This is the first I’ve heard of the issue. Without a lot of troubleshooting, it’s hard to determine whether the conflict arises from us or them, or no one – just a conflict.

I will say I’ve bumped into conflicts with optimization plugins a few times. They re-compile, re-minimify, and combine our JS files with other plugins or core files. Doing so can often interfere, for example, with the order in which scripts load.

That said, usually when this happens, functionality breaks immediately. In your case, it sounds like some functionality works for some number of images and then suddenly stops.

In any case, one way you can often work around this is just to exclude our scripts from Autooptimize. They have documentation for doing this on their WordPress.org page here. Is that something you’ve tried?