Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter robyy94

    (@robyy94)

    edit: i’ve founded this error in the console:

    Uncaught TypeError: undefined is not a functiontribe-events-ajax-list.min.js?ver=3.9.1:1
    (anonymous function)jquery-1.7.2.min.js?ver=1.7.2:2 f.Callbacks.ojquery-1.7.2.min.js?ver=1.7.2:2
    f.Callbacks.p.fireWithjquery-1.7.2.min.js?ver=1.7.2:4 wjquery-1.7.2.min.js?ver=1.7.2:4
    f.support.ajax.f.ajaxTransport.send.d

    Brook

    (@brook-tribe)

    Howdy robyy94,

    It looks like you are spot on. I just tested your site while logging network requests. The Ajax request is sent properly, and it gets the correct response with the next page of listings. However, that JS error, and especially the followup one that Firefox shows, prevent it from parsing the request.

    In simple terms this basically means that you have a JavaScript conflict. I realize you have already tested for conflicts, but it seems that something must have happened during the last conflict test that did not full purge past data. Some semi common things that can happen:

    • Many caching plugin/solutions have special deactivation and removal steps beyond just disabling. Frequently they require your to purge the cache before deactivation, sometimes delete a folder, etc. If you have ran one at any point in the past, you should check with Google for these instructions. THey frequently cause JS conflicts due to their desire to optimize JS files. Unfortunately many plugins, like ours, already optimize our files and do not behave properly when you try to reoptimize.
    • Your browser’s cache had the old JS file. It needs to be cleared during the conflict test.
    • Folks try switching a theme, then they switch it back to the original, then they disable plugins. They should all be disabled at once for a full conflict test.

    Sometimes it’s all of the above. Either way, if I were in your shoes I would carefully redo a conflict test. In addition to those tips, this guide can be rather helpful for the proper procedure. Test For Conflicts. Once you know what the conflict is, frequently it can be fixed. Sometimes someone with the same plugin or theme already has posted a solution. Sometimes you just need to disable a setting, like Minification in the caching plugin. But, first you pretty much need to know what is causing the conflict, or else it’s just stabs in the dark.

    I hope that helps. Cheers!

    – Brook

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘List view not load previus event’ is closed to new replies.