• Resolved robkm

    (@robkm)


    Since the last Photonic update, I have a problem opening photos in Swipebox. When I click on a photo it takes me to a URL that does not exist, instead of opening in Swipebox.

    i.e. https://mysite.com/somepage/gallery%5Bpicasa-stream-1%5D/1/

    I think (but I’m not sure), the problem has to do with “FancyBox 2” being selected under “Non-bundled Lightbox libraries” on the settings page, which I didn’t select and CANNOT un-select.

    Any ideas?

Viewing 10 replies - 1 through 10 (of 10 total)
  • Plugin Author Sayontan Sinha

    (@sayontan)

    Any chance of a URL?

    If not, can you try disabling deep-linking? You can do it from Photonic → Settings → Generic Options → Generic Settings → Deep Linking.

    Fancybox2 has been an option in the plugin for quite a few years – it only comes into action if you select the “Non-bundled lightboxes” option (see here).

    Thread Starter robkm

    (@robkm)

    I tried to disable deep-linking and no change. Here’s a link to an example page https://bit.ly/2iyQaUu

    Thank you!

    Plugin Author Sayontan Sinha

    (@sayontan)

    Is there any caching plugin active on your site? The reason I ask is because there are a couple of variables that I am not seeing on your website. When I go through the page source for the link you provided, I see a variable called Photonic_JS, which should have two elements – deep_linking and social_media. I am not seeing any of them.

    Plugin Author Sayontan Sinha

    (@sayontan)

    OK – so here’s what is probably happening:

    1. You might have some sort of a caching plugin that needs to regenerate the pages. The two variables that I mentioned above control the deep-linking behaviour, and are set by the back-end for the front-end. If you turn off deep-linking and that gets reflected in the front-end, you should be fine.
    2. The reason deep-linking itself isn’t working is because of a script that is being loaded by your theme (autoloadpost.js), which seems to be killing the # in the deep-link, resulting in the links getting distorted. When I click on a thumbnail to show an image, for the briefest moment it shows up in Swipebox, then the URL gets changed and you get the 404 error.
    Thread Starter robkm

    (@robkm)

    To secure my site, I use Wordfence, which has caching capabilities. I don’t use them, however. And even after disabling Wordfence all together, I still have the same problem. :-/

    Thread Starter robkm

    (@robkm)

    OK I have narrowed it down to a problem with Swipebox. I have tried all the other pre-installed lightboxs and they all work except the aforementioned.

    Plugin Author Sayontan Sinha

    (@sayontan)

    Weird. I was pretty sure the problem was due to caching. Basically, if you see here, the two variables should show up.

    I can give you a workaround for now, but if we were able to disable deep-linking that would have been the least messy solution. If you go to photonic.js line 90, you can replace this code:

    if (Photonic_JS.deep_linking == 'none') {
    	return;
    }

    With this:

    if (Photonic_JS.deep_linking == undefined || Photonic_JS.deep_linking == 'none') {
    	return;
    }

    Similarly, for line 44, replace:

    if (Photonic_JS.social_media == '') {
    	return;
    }

    With this:

    if (Photonic_JS.social_media == undefined || Photonic_JS.social_media == '') {
    	return;
    }
    Thread Starter robkm

    (@robkm)

    I went back to version 1.57 for now. Everything is back to working fine. If I get the time, I may apply that workaround you provided.

    Thank you for taking time out of your day to help!

    Plugin Author Sayontan Sinha

    (@sayontan)

    Can you let me know if 1.59 fixes this?

    Also, I made some changes to the Picasa integration, with respect to authentication. See here and here. This will make it a lot easier to determine album ids and display protected content etc.

    Plugin Author Sayontan Sinha

    (@sayontan)

    I am guessing this is no longer an issue. I am going ahead and marking this thread resolved, unless you think there is something I still need to fix.

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘New issue since last update’ is closed to new replies.