Viewing 14 replies - 16 through 29 (of 29 total)
  • By the way, @archetyped, thanks for fixing the view on mobile phones like my Ipad 5, awesome ! And thanks for naming it to after my other handle zephyr88.

    Now, only problem is to get this BWP thing solved. One problem fixed, another one came, argh. BWP takes precedence however, as it covers other plugins too. Earlier Simple Lightbox is fine, so I’ll probably revert to that first.

    By the way, is there any script handle name for the SLB lightbox javascripts ?

    simple-lightbox/client/js/lib.core.js
    simple-lightbox/client/js/lib.view.js

    Then maybe I’ll put them in the ignore list of BWP and see if it works … I can only put in handle names, not script names …

    Plugin Author Archetyped

    (@archetyped)

    Currently the handles for each file are:

    slb_core – lib.core.js
    slb_view – lib.view.js

    Perfecto !

    It doesn’t work if I ask BWP to ignore it, but it works when I put it under “scripts to be minified in header”. I can live with that, and I’ll just ask BWP why.

    Thanks !

    In the meantime, I go back to previous version, as I like the wider area for moving next or previous, as well as the captions. Both reported in issues, under Github.

    And here is hoping the rest of the guys here get their problem fixed …

    Thread Starter l7world.com

    (@l7worldcom)

    Got it to work but also had to disable JS minify in cache.

    Also there’s no longer a next or previous text link?

    It’s also broken for me.

    It looks like the new AJAX stuff is incompatible with a CDN (also part of W3 Total Cache).

    Using S3, you get:

    XMLHttpRequest cannot load tag.item.js.gzip. Origin is not allowed by Access-Control-Allow-Origin.
    XMLHttpRequest cannot load tag.ui.js.gzip. Origin is not allowed by Access-Control-Allow-Origin.
    XMLHttpRequest cannot load handler.image.js.gzip. Origin is not allowed by Access-Control-Allow-Origin.

    See onlysoundingout.com for an example.

    Also, what’s now being shown as the description under the image, looks like the filename?

    How do I change back to the old version?

    Thanks

    Plugin Author Archetyped

    (@archetyped)

    Thanks for the feedback. However, I’m not getting the same error you’ve posted. Those files appear to be loading properly. Can you provide a bit more info on the OS/browser you’re using?

    The lightbox displays the title for the image from your site’s media library. By default, WordPress uses the file’s name (without the extension) as the title when the image is uploaded if a custom title is not set. All titles can be edited from within the media library.

    All previous versions are always available on www.ads-software.com’s Simple Lightbox page

    Yeah, I turned off caching completely as your new version just doesn’t work with CDN support. I’ve turned it back on to show you. Can you have a look now please?

    Plugin Author Archetyped

    (@archetyped)

    Thanks, I’m still not getting the AJAX error you’re getting. Those files are loading properly when I load the page. What OS/browser are you seeing this error in?

    However, I can confirm that SLB is not currently working on your site. It appears that W3 Total Cache rewrites the image image links to the CDN after SLB processes them. I’ll take a closer look at this and thanks for the feedback!

    I fixed the original error by setting up a Cross-Origin Resource Sharing (CORS) policy – see here. Now it’s something else. Haven’t really got the time to look into it but just to say, I’m finding starting to find the *simple* lightbox somewhat misnamed..

    Plugin Author Archetyped

    (@archetyped)

    Ah, yes, that makes sense. SLB of course cannot (will not) support every 3rd party modification, so it’s best to follow the recommendations provided by these service providers.

    I assure you SLB itself is quite simple, but when adding more complex modifications things like caching and CDNs to your site, things do tend to get a bit more complicated ??

    Do you think there is a way to manually get things to work?

    Plugin Author Archetyped

    (@archetyped)

    Sorry if I wasn’t clear in my previous posts.

    The AJAX error was a configuration issue related to the 3rd party CDN. This is something SLB has no control over and must be resolved using the method you already used.

    The link modifications by W3 Total Cache is something that will be investigated further though.

    Just to update you, I’ve downgraded to version 1.6 and it works fine with the CDN, and W3 Total Cache out of the box.

    It may help you make the improvements to version 2. Results can be seen here.

Viewing 14 replies - 16 through 29 (of 29 total)
  • The topic ‘Doesn't work after update’ is closed to new replies.