Slideshow/Lightbox contains double the images

Hi @sparky672,

Can you please let us know what Lightbox effect are you using?

I need to specify here that SimpleLightbox doesn’t stop at the images of a specific gallery and it will load the images of all the galleries that you have inserted on that page so perhaps you have inserted the gallery twice and that’s why SimpleLightbox loads the images twice.

ONE insertion. ALL lightbox options exhibit the same bug. I’ve since added more photos, but you can see it here.

https://www.no2northpoint.com/no2np-marches-in-manhattan-parade/

In this case the first thing to check is plugin conflicts.

Please deactivate all your plugins except for nextgen gallery. See if this fixes the issue. If it does reactivate one plugin at a time and check after each to see which one brings the issue back.

Please keep us posted.

Sorry… production site with high traffic. Would be easier for me to shut down NextGen since it’s only used on this one page than any of the other plugins.

However, since this stuff is controlled by JavaScript, it would be easy for you to examine the DOM from the link I provided and work backwards from there.

Hi @sparky672,

Both Basic Slideshow and the Lightboxes will display the images in loop mode so it won’t really stop when getting to the last image from the gallery but automatically switch to the first one. Hope that this explains the behavior.

Both Basic Slideshow and the Lightboxes will display the images in loop mode so it won’t really stop when getting to the last image from the gallery but automatically switch to the first one. Hope that this explains the behavior.

That’s absolutely false and I could have never known anything was amiss if that were true.

Just go to the link I posted and bring up lightbox. There is an ending slide and a starting slide where you will not get an arrow and will not be able to “loop”. The entire photo collection is displayed twice within the lightbox when you hit the “last” slide. (slideshow has 18 photos and lightbox shows them all twice for a total of 36 before you cannot click any further)

It’s not a major issue, but it’s definitely an issue and I think you two should take it more seriously; at least get your stories straight. Thank you.

Hello @sparky672,

Apologies, it will be ideal if you could send us the shortcode you are currently using.
Your shortcode should be visible if you edit the block or page with the HTML preview.

Here is an example of how our shortcodes work: https://www.imagely.com/docs/nextgen-gallery-shortcodes/

And here is an example on how you can check the code
https://www.imagely.com/docs/nextgen-shortcode-generator/

That information will perhaps provide the id of the gallery that you are currently using, sort order, and if it is an outdated shortcode.

Feel free to write us back; we are happy to help!

That information will perhaps provide the id of the gallery that you are currently using, sort order, and if it is an outdated shortcode.

I used the green ngg icon in my editor to automatically create/add the gallery. I did not write the shortcode by hand.

Inspecting the editor HTML of that page shows this shortcode…

[ngg src=”galleries” ids=”2″ display=”basic_slideshow”]

I only have one gallery ID 2 and it contains 18 photos. See screenshot…

https://i.ibb.co/bvG0ScR/Screen-Shot-2020-03-11-at-11-13-27-AM.png

As a fellow user, I found your posts interesting because I’ve used basic slideshows on my site with arrows enabled and it loops, just as they said it does and you can’t turn it off. It’s a lightbox issue. It does it automatically. Here’s an example, and I sped it up to see the rollover. I was wondering if perhaps there was a way to limit the number of loops based on your post, but I don’t see any.

https://polywogg.ca/pandafamilygallery/2008-pw-1e-cake-tasting-copy/

You seem pretty knowledgeable, and the layout is pretty clean on your site, so I find it strange that you are avoiding the normal procedure for debugging a potential conflict, which is to temporarily disable all the plugins and test only on a default theme to see what is conflicting. It’s relatively easy even to do it “batches” i.e. deactivate all, reactivate 5 at a time, until the conflict reappears, and then test within those 5.

Most people can find the conflict in about 10-15 minutes. Yet you refuse to do that and want them to “work backwards from your code”…not sure how you expect them to guess where the conflict is coming from based on hte JS, particularly as it works on other sites exactly the way it is supposed to.

My guess, FWIW, is one of four possible glitches:

a. Another plugin (like JetPack galleries) is conflicting with NextGen and both are triggering lightbox;
b. Your video on that page is interacting with lightbox and causing it to load two copies but no more (I’ve had issues before with lightbox when galleries and vids were on the same page with other plugins, not with NextGen though);
c. Your memory allocation is loading two sets for the loop, which might fall into a larger “server configuration/limitation” issue; or,
d. A JS / Ajax pagination error that is treating the images as pages, likely a result of another plugin.

Good luck…if you find a way to turn it on/off, would love to know.

P.

find it strange that you are avoiding the normal procedure for debugging a potential conflict, which is to temporarily disable all the plugins and test only on a default

It’s a live site presently getting a ton of traffic. What’s so strange about not wanting to disrupt this? Even 10 minutes could be a loss of of enough people to affect social media reach. One lost Facebook share within that 10 minutes could mean hundreds of people not reached.

Secondly, it’s working. It’s not ideal having it loop twice and stop, but it’s serving its purpose. Therefore, not a priority for me to disrupt the site, even for 10 minutes.

a. Another plugin (like JetPack galleries) is conflicting with NextGen and both are triggering lightbox;

If I had another lightbox installed, I’d try using it instead. JetPack is not even installed here.

b. Your video on that page is interacting with lightbox

I had this problem before I embedded the Google video.

c. Your memory allocation is loading two sets for the loop

The lightbox is 100% JavaScript (client-side) code so not sure how server config could ever affect that.

d. A JS / Ajax pagination error that is treating the images as pages, likely a result of another plugin.

I don’t know what that means. If they weren’t being handled as images, the lightbox wouldn’t work, AFAIK?

If I get a chance to look a the DOM, I’ll report back what I’m seeing, if anything.

Thank you for the detailed response and suggestions.

• This reply was modified 4 years, 8 months ago by sparky672.

Hi @sparky672,

It appears that in your case slick slider creates clones for every slide and it may be somehow related with the “Transition Style” that you are using.

Please access “Gallery -> Gallery Settings” and try to set “Fade” for the “Transition Style” then save the options and check again. Looking into the code, I am assuming that this should prevent the Slick slider from generating those clones.

Please let us know

It appears that in your case slick slider creates clones for every slide and it may be somehow related with the “Transition Style” that you are using.

Yes. That was it. I changed it to “Fade” and it’s working as expected now.

So we found a bug, right? After all, Slick Slider is part of NGG and “Slide” is “the “Transition Style” that I am using” only because it is the default option!

Hi @sparky672,

I understand but I am afraid that we will not be able to do much in this specific case since what we are doing is we are using slick.js and fancybox.js scripts in our plugin and this is something that is more like a problem between how these are working together when a specific transition style is being set. I need to note that the transition style is not ours but it is just a slick.js parameter that we are passing from NextGen.

You can have a look at this article to see that there are lots of other reports concerning slick.js that’s cloning the slides if using a specific transition style in combination with the infinite scroll https://github.com/kenwheeler/slick/issues/940

The problem resides in the fact that Fancybox isn’t set to infinite loop the images, unfortunately, so that’s why it scrolls through all the regular images then through all the cloned images and the stops ( giving the feeling that it displays duplicate images )

I would just switch to SimpleLightbox effect to solve this incompatibility aspect.

• This reply was modified 4 years, 8 months ago by Mihai Ceban.

I need to note that the transition style is not ours but it is just a slick.js parameter that we are passing from NextGen.

What I think you are not understanding is that I am not doing anything special or reconfiguring the options outside of your normal defaults. I select my gallery and insert a “Basic Slideshow”. At this point, no matter which lightbox option I select, there is this issue. I have to select “Fade” on the slideshow transition in order to get around it.

You can have a look at this article to see that there are lots of other reports concerning slick.js that’s cloning the slides if using a specific transition style in combination with the infinite scroll

Why are you integrating slick.js into your product if it has these problems? Surely, there is something better you can use. At least take a little responsibility for the lackluster user experience.

Instead of blaming others…

1. Reconfigure your own GUI so a combination of incompatible options cannot be selected in the first place.
2. DO NOT make these options part of the default settings.
3. Or just integrate a better slider plugin – one without these bugs.

Like I said, it wasn’t a big deal and I just wanted to report it… but getting to the bottom of this was really painful.

Thanks for the report – this was something new for me too since I haven’t heard of any other reports from the past ( maybe because the majority are using the default SimpleLighbox instead of changing to Fancybox ) but I agree with your point about either excluding the “Slide” transition style or defaulting it to “Fade” to avoid any further confusions ref it.

I have submitted an issue report for our developers and we hope to review and take actions ref this case in one of the future updates.

Sorry for the inconveniences

• This reply was modified 4 years, 8 months ago by Mihai Ceban.