WordPress 4.7 compatibility with WordPress images

  • Resolved ACEkin

    (@acekin)


    7 years, 12 months ago

    I am back! This time with a different problem, Easy FancyBox does not seem to work with images inserted from WordPress. I have tested this on different posts and the result is the same, the clicked image opens in the display port by itself rather than on an overlay.

    NextGEN Gallery images seem to work fine. I have tried different NG overlay settings, like None, Fancybox, Custom, and that does not seem to make any difference in how EFB handles WordPress images. You can see the effect on my site, in the Irving Penn post as well as in the post Photography and Language, 3. The links below are for a replica site where I upgraded WordPress to 4.7:
    https://www.testbeds.info/irving-penn-at-lesley-university/
    https://www.testbeds.info/photography-and-language-3/

    The same posts on my regular site work fine with Easy Fancy Box.
    https://www.keptlight.com

    My EFB settings on the testbed site are in the screen capture at the following link:
    https://www.dropbox.com/s/jv40lggfb0x1bwb/fancybox1.jpg?dl=0

    By the way, the center on scroll still misbehaves on demand but I am not worried about that at all.

    Cemal

Viewing 13 replies - 1 through 13 (of 13 total)

  • Your test site seems to be working fine. At least in the Chrome browser (latest)… What browser are you using? Are you logged in or out when testing the front end?

    Thread Starter ACEkin

    (@acekin)

    I am using FireFox and tested in MS Edge, neither works and function as I described. Logged in in Firefox but not in Edge.

    Cemal

    • This reply was modified 7 years, 12 months ago by ACEkin.
    Thread Starter ACEkin

    (@acekin)

    I logged out from FireFox instance and it did not make any difference. Yes, it does work in Chrome.

    Cemal

    I notice you have click tracking enabled in Slimstat. Could you disable that?

    Thread Starter ACEkin

    (@acekin)

    I disabled SlimStat and Fancybox started working. Then I enabled SlimStat and turned off Tracking in the options. That also made Fancybox work. Now, the question is will the users of SlimStat be advised to turn off tracking or do you have a fix up your sleeve? Thank you for spotting the problem.

    I will keep this thread open as unresolved in case you have other things for me to try.

    Cemal

    And please visit https://demo.status301.net/ in Firefox and Edge. It’s running 4.7 and the latest plugin there too…

    OK strike that. The issue is Slimstat as you discovered.

    I remember somebody mentioning a work-around but I don’t know where to find the how-to. Is there a Slimstat support forum or documentation somewhere?

    Thread Starter ACEkin

    (@acekin)

    I am OK for the time being to turn off tracking in SlimStat, especially on my test site which is not crawled or visited anyway. Now I know if I upgrade on my live site to WP 4.7 I will turn off tracking. I am not exactly sure what I will miss, if any.

    I am taking too much of your time by finding problems. Sorry about that, but I think it is better to know the problem before it becomes too big.

    Thanks again, feel free to mark this as resolved if there is nothing for me to test for you.

    Cemal

    Hi, Slimstat support here. Please take a look at our knowledge base to learn how to configure Slimstat and avoid conflicts with your lightbox library:

    https://slimstat.freshdesk.com/support/solutions/articles/5000528534-i-noticed-a-conflict-with-your-lightbox-library-here-what-can-i-do-

    Best,
    Jason

    Thread Starter ACEkin

    (@acekin)

    @jason, thank you for chiming in and pointing me in the right direction. I have added fancybox in the box “Do not track” and all seems to be working fine. It is a fix for the suddenly emerged problem. I have no idea what WordPress 4.7 has to do with all this though.

    Thanks,

    Cemal

    I’m glad it worked ??

    Best,
    Jason

    Hi Jason, thanks for chipping in ??

    Great solution! Will add this to the readme ??

    Thread Starter ACEkin

    (@acekin)

    I tried it on my live site with the same workaround and it worked. So, adding fancybox to the do not track field in SlimStat works. I wish these would not even emerge but finding a workaround in short order has been very good, thank you both.

    Cemal

    Unfortunately because of how Javascript operates, we have no way of telling if any other event handler is attached to a link, and selectively run the tracker only on those that are ‘clean’. So this seems to be the most reasonable compromise ??

    Jason

    • This reply was modified 7 years, 12 months ago by Jason Crouse.
Viewing 13 replies - 1 through 13 (of 13 total)
  • The topic ‘WordPress 4.7 compatibility with WordPress images’ is closed to new replies.