Plugin WAS working but stopped, not sure what changed…

  • Zhivagooo

    (@zhivagooo)


    8 years ago

    Hello,

    This plugin was functioning fine, some sometime in the last day stopped working.

    My website is fandomfashions.com and my settings are as follows:

    Nav Selector: .woocommerce-pagination
    Next Selector: .woocommerce-pagination a.next
    Item Selector: li.product
    Content Selector: ul.products

    I’ve gone through my page and I haven’t done anything to alter any of the anchors but I can’t figure out where the issue lies. Can someone help me out? Thank you in advance. ??

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author YITHEMES

    (@yithemes)

    Hi,
    Do you have recently activated a new plugin or a cache system that minify the javascripts?
    There are two JS error on console that block correct scripts executions.
    The errors are:
    minify-b1-jetpack-photon-4cb8768….js:1 Uncaught SyntaxError: Unexpected token <
    minify-b1-jquery-selectBox-95a2fdd….js:1 Uncaught SyntaxError: Unexpected token <

    Try to disable the js minify and check if the error persist.

    Thread Starter Zhivagooo

    (@zhivagooo)

    Hello,

    Thank you for looking into this. I have been unable to return to this until now, unfortunately.

    I did not add any new minification or caching, everything is the same as when I originally set up the Infinite Scroll and when it was functioning.

    I have disabled jsminify on the two scripts you’ve mentioned but there has been no change.

    I also tried emptying my caches.

    Plugin Author YITHEMES

    (@yithemes)

    Hi,
    as I see on console you still have errors.

    GET https://cdn2.fandomfashions.com/wp-content/plugins/bwp-minify/cache/minify-b1-wc-add-to-cart-56ff3e963044d4413f398e541a444d9c.js 400 (Bad Request)
GET https://cdn2.fandomfashions.com/wp-content/plugins/bwp-minify/cache/minify-b1-jquery-yith-wcwl-5b43381d6f05d489130dbcbb474b11cb.js 400 (Bad Request)

    If you have disabled jsminify please purge completely cache and cdn.

    Regards ??

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Plugin WAS working but stopped, not sure what changed…’ is closed to new replies.