Firelight

Hi Per,

Thanks for the report.

The 2.2.10 release made minor changes to the pro landing page in the admin area. It’s unlikely – basically impossible – that the changes in that specific release would have affected slideshows on specific browsers.

I did just test this, tho. I found that Fancybox Classic Reloaded auto slideshow / automatic image change is working fine on Chrome in 2.2.10. But for Fancybox V2, it is not. I rolled back and tested 2.0.6, and that also isn’t working for V2. So there’s a bug. I’m not quite sure when it was introduced. I will need to investigate.

A couple questions:
* Which lightbox are you using? (ie, Classic Reloaded, Legacy, or V2)
* When you updated, did you update from an older version? I’m wondering if you skipped past multiple versions and that’s why you’re seeing it now with 2.2.10.
* To confirm, when you say ‘automated image change’ your talking about the option named ‘Auto play slideshow’ correct? So you’re expecting your the lightbox to automatically flip through images once open.

In any case, there is at least some kind of bug here that I will fix. I also just want to be sure that what I’m fixing is the specific issue you are seeing.

Unfortunately, I’m out of town this week with limited time. But I will try to get a release out with a fix for this early next week.

Thanks.

Hi @alithewpdev – On the assumption that excluding the files above will work, I’m going to go ahead and mark this thread resolved. Obviously, if it is still not working, let me know and I’m happy to troubleshoot further.

Hi @junior,

I know this is obvious, but just to be sure, can you please confirm that you are using the latest version of the plugin (2.2.8)?

There was an issue with saving options for a subset of users a couple weeks ago, but that was resolved. I suspect you’re having the same issue. If you are fully up-to-date, and still cannot save, we’d need to troubleshoot. It’s likely to be something specific to your environment as the lightbox, including saving option, is working well for us and most users.

Also to confirm, when you say it ‘will no longer work’, do you mean that saving/updating options is not working, or that the lightbox is not opening images on the front end after you save?

Hi @alithewpdev –

It’s been a while since I worked with WP Rocket. I just did some searching myself. It looks like you could exclude all of the Easy Fancybox JS by adding this to their exclude field:

/wp-content/plugins/easy-fancybox/(.*).js

I took that line from this page. This page also suggest you can test a page without WP Rocket’s extra minification by add ?nowprocket to the end of the url for any page.

https://docs.wp-rocket.me/article/915-find-the-right-js-files-to-exclude-from-minification

It might be worth trying both of those options to see if we can get the plugin working. If so, we’d confirm that it is a plugin conflict. If needed could narrow down which exactly JS file is causing issues in your case.

@shaunbowen – I see the issue. Basically the lightbox navigation hovers on top of the video controls, so you can’t click on or work with the video controls. I need to think about what the best solution is that for the long term – one that solves it here but doesn’t introduce unwanted changes when they’re not needed.

For now, I’m wondering if you can try adding the following CSS to your site? This reduces the size of the area for the lightbox nav controls. Note that while this will make your vimeo controls accessible, it means that to get the lightbox controls to show, you have to hover over a smaller space closer to where the arrows appear. This css will also apply to all instances of fancybox lightboxes on your site, not just where you’re using it open vimeo galleries.

.fancybox-nav {
    height: 150px;
    top: 50%;
    left: 50px;
    transform: translate(-50%, -50%);
    width: 100px;
}

.fancybox-next {
    right: -50px;
    left: auto;
}

Oh, interesting. So we know it can be working correctly. That’s quite helpful for troubleshooting.

Here are the PDF settings on the Fancybox V2 demo (at https://firelightwp.com/free-lightbox-v2/). And yes, would be worth duplicating that to see if it behaves differently. If it is a setting that is causing the difference, I suspect it is the ‘Embed with’ setting. But let me know.

https://d.pr/i/qSOy6Y

Hi! Thanks for the input and feedback. We will certainly take a look at this. I know there are some other accessibility improvements we’ve been wanting to make as well.

Nice review. Thank you!

On your point about the pro lightbox not doing everything you need, I’d love to ensure that it does. Ideally, the pro lightbox should do *everything* the free ones can do, plus the extra stuff it does.

As is, the pro lightbox is only a month old, and will be getting very active dev attention in the coming months/years. So feedback and feature requests are very welcome!

Based on your note, I *think* that the features you are needing are:
* group images based on rel attribute
* get and display image title based the thumbnail alt attribute

Is that right?

The ‘use alt as title’ setting is something I’m already working on. I think that will likely be in the next release. I would think we could also include gallery grouping based on rel attribute.

On a broader note, I must admit that when creating the pro lightbox, I just assume most people are now adding galleries/images via the block editor rather than (a) short codes or (b) html. It sounds like you may be using html.

I need to review things and make sure you have the same flexibility in crafting html that can be digested and used by the pro lightbox, and also be sure that is all in the documentation.