• Resolved Kasia

    (@kasia_codeword)


    I have both NextGEN and WooCommerce active on my site. Hard to tell exactly which version of WooCommerce is where the conflict began, because my client only just reported the problem. When NextGEN is active and the user is attempting to check out with Safari on macOS or iOS, when the user gets to the “Place Order” screen the AJAX spinner just spins on and on and on, and the error console shows the following:

    TypeError: null is not an object (evaluating ‘o.reload’)

    The issue only seems to be present on Safari. Everything works fine on Chrome. When NextGEN is deactivated, everything works fine.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Contributor Imagely

    (@imagely)

    @kasia_codeword – WooCommerce itself can be quite involved and as such there is not enough context to know what might be the specific issue as most generic testing with NextGEN Gallery and WooCommerce works fine across all browsers.

    Is there anything more you can offer? Are you testing with a something like the “default” WooCommerce theme, NextGEN Gallery and only the base WooCommerce plugin active?

    Thanks!

    – Cais.

    Thread Starter Kasia

    (@kasia_codeword)

    It appears that a clean WordPress install running only WooCommerce and NextGEN with the TwentySeventeen theme does not throw an error. Unfortunately, the live site where the problem occurs is running on a custom theme with many other necessary supporting plugins. I did activate the TwentySeventeen theme on this site when I was trying to figure out the problem and still experienced issues, so I’m guessing that perhaps there is another plugin that might be contributing to the problem. Because the gallery is a very minor feature of this site, it would not be a good use of resources to spend a lot of time trying to determine where the conflict is. As such, I have replaced NextGEN on this website with a different photo gallery plugin that isn’t causing any conflict with WooCommerce. Thanks anyway.

    Plugin Contributor Imagely

    (@imagely)

    @kasia_codeword – Thanks for the follow-up.

    – Cais.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Conflict with WooCommerce while using Safari’ is closed to new replies.