Additional notes from me: I tried disabling plugins, but it changed nothing. I tried a different theme and it changed nothing.
@andyt8 – As you are seeing this work elsewhere in a similar circumstance are you able to compare the two site more closely to see what differences there may be between the two?
I would suggest looking at the server environments as you are indicating you have checked your current active plugins and theme to see if the conflict is there.
Thanks!
– Cais.
Hello Cais, thank you for your answer.
I’ve started comparing both websites, but until know I have not found any differences exepct of colour and similar settings.
At the moment I don’t know how to get further. In most cases, the lightbox appear if I use return button in webbrowser after a mouse click on a picture.
Really strange situation…
regards, Andyt
@andyt8 – Thanks for pointing our the “back” button reference, I did not notice that earlier. What appears to be happening is clicking on the image is triggering two events. The first event is the Fancybox (which appears to be working correctly) and the second event which is ignoring the Fancybox and just treating the image as is (which displays the image as the default HTML <img> tag would).
In most cases, this points to an option / setting / feature set of the theme (most common) or another active plugin that specifically deals with images. I would recommend focusing on those types of items to see if you can sort out which specifically is causing the second triggered event when clicking on an image.
Thanks!
– Cais.
Hello Cais,
Thank you for your answer. I will go in that direction. Maybe I found something in the next days. I will response if I found the solution or not…
regards, Andyt
@andyt8 – Thanks, please let us know what you find.
– Cais.
Today I was able to fix the problem.
It had nothing to do with my plugins or my theme. Something strange, but it was a problem from a javascript which do statistics processes.
The external javascript is an external integration from Slimstat Analytics, which belongs to an other WordPress installation.
So my conclusion about problems with lightbox and similar… – maybe an external javascript-code from external statistics and analytics service produces the problem.
regards, Andyt
@andyt8 – Thanks for the update on this!
– Cais.
Hi,
Slimstat support here. This issue has been resolved a while ago. If you think Slimstat is causing this conflict, you might be using a quite old version of our plugin, and we would like to encourage you to upgrade.
Best,
Jason
Hello Jason, nice to get a response from you. I used the latest version of slimstat on the original WordPress installation. There were no problem.
The other WordPress installation with NextGen gallery used Slimstat as external integration, but I did not use CDN for wp-slimstat.min.js. All http/s connections should be from the same main domain.
Therefore I did a copy of that file to host it on my domain. That version was too old and was updated for some days. It look like I forgot to check it. However, wp-slimstat.min.js from SlimStat installation isn’t the same from CDN. I tried the file from plugin folder for some months, but external integration didn’t work – only with file from CDN.
regards, Andyt
That’s strange. Usually the CDN should automatically sync with the WordPress repository, every time we push a new version. I will look into that. Thank you for pointing it out! Other than that, is it working now?
Best,
Jason
Hello Jason,
Yes, at the moment it work without problem.
regards, Andyt
@coolmann – Thanks for weighing in on this topic!!
– Cais.
