Viewing 7 replies - 16 through 22 (of 22 total)
  • NGG is very popular and therefore used with a wide variety of third party plugins and themes. Some plugins and themes decide to use their own version of jQuery. That isn’t necessarily a problem if the author decides to do that correctly by enqueuing the same version of jQuery but would like to load jQuery from a CDN. But it does become a problem when a third-party plugin/theme overrides to enqueue a different version of jQuery that changes the API interface such as what happened with jQuery 1.9 over 1.8. When that happens, things break. If you look at the definition of wp_deregister_script(), you can see that WP had to do it’s best to stop users from specifying their own jQuery versions in WP-Admin. Although they allow it on the front-end, they discourage it.

    It would be very difficult for us, if not practically impossible, to determine if a particular plugin or theme is overriding the bundled version of jQuery for good reason. In any case though, if a plugin/theme needs a custom jQuery version they should enqueue it as a different handle, such as ‘jquery-custom’, rather than override the ‘jquery’ handle WP provides.

    The fix_query() method in NGG resets the ‘jquery’ handle back to what WordPress shipped with. That is, the ‘jquery’ handle should have no ‘src’ attribute but instead have ‘jquery-core’ as a dependency. The ‘jquery-core’ handle should have a src of ‘/wp-includes/js/jquery/jquery.js’.

    Resetting the handle back to how WP intended seems to resolve most of the cases we find, though there will be cases where it doesn’t work. It’s a very difficult problem to resolve in a general way due to the wide matrix of possible plugins/themes that NGG could be installed alongside. If there’s a better way of handling this, we’re open to suggestions.

    For the cases in which resetting the ‘jquery’ handle back to what WP shipped with doesn’t work, our support staff will do their best to help determine what the problem might be and relay any details back to the developers for a solution. Your assistance and co-operation is much appreciated. Our goal is to be widely-compatible as possible.

    Thanks,
    Mike

    Same for me : after updating https://clouderial.com is broken !

    Many thanks to @steve for your solution that works for me… You save my day and my site. Hope that an official fix will be soon available.

    Clouderial’s Team

    Plugin Contributor photocrati

    (@photocrati)

    @jmcollin92 – Although @steve’s work-around may be solving your initial issues with this, I would recommend updating to our latest beta version which takes into account much more than what Steve is suggesting.

    See this page for more details: https://www.nextgen-gallery.com/nextgen-gallery-latest-beta/

    Thanks!

    – Cais.

    Why do you have to break our sites every update? Why?

    I am having the same problem. Am using the PullOut Widget plugin, which worked before I loaded Nextgen onto the site. If I disable nextgen then it works again. Have just uploaded the new beta version as recommended above must no joy I’m afraid.
    Thanks Helen

    Plugin Contributor photocrati

    (@photocrati)

    @wizontheweb – As you are referring to a different issue you should start your own topic.

    Thanks.

    – Cais.

    @wizontheweb – I’m not so sure it’s not the same issue, it debends. If you experiencing that no jquery loads, so not just only 1 plugin is broken that uses jquery and NextGen lightbox not works eighter then I’m pretty sure it’s the very same issue.

Viewing 7 replies - 16 through 22 (of 22 total)
  • The topic ‘V 2.0.57: Plugin jQuery Lightbox does not work anymore’ is closed to new replies.