Broken "next page" links (sometimes)

Forums › Forums › Search & Filter Pro › Broken "next page" links (sometimes)

Viewing 6 posts – 11 through 16 (of 16 total)
  • Anonymous
    #14303

    Hey Ross,

    Just wanted to let you know that I rolled back to the non-ajax version for now.

    I did a bit more investigating and it seems like the ajax request works, but is simply opening in a new page instead of updating the current page.

    If you can think of any other tests I can do to troubleshoot, let me know and I’ll try them.

    Thanks,
    Greg

    Ross Moderator
    #14306

    Hey Greg, I’ll come back on to this soon and see if I can see whats going wrong.

    Thanks

    Anonymous
    #14388

    Thanks, Ross, I really appreciate it.

    I disabled ajax on the main site, but I set up the dev site so that you can see the problem. The way to see the problem is to go here:

    http://www3.calvaryem.org/media/sermons-archive/

    Select “sermons” under content type in the filter, select “Joseph Babij” under speakers in the filter, then try to go to “next”.

    The resulting page returns the right AJAX result but it returns it in its own new page, not embedded in the parent page.

    Thanks,
    Greg

    Anonymous
    #19812

    For what it’s worth, I’m encountering this exact same problem, and I’d love to see it working properly.

    The page is http://frederickblock.com/product-catalog-search/

    If you check “brick,” then use the “next” link to go to page 2, you will go to a page that loads only the results — no template, header, styles or anything else.

    If you check “brick” then check “building stone” then uncheck “building stone,” the pagination seems to work fine.

    I’m not sure what to do to fix it.

    Anonymous
    #19815

    Ah! For what it’s worth, I found the answer. Hopefully this, as well as the thread on which I found my solution, will help.

    On the display results tab, my pagination selector was incorrect! Instead of having “.pagination a” for some reason I had changed it to “.pagination > a” which doesn’t work because the “a” tag is not a direct child of the “.pagination” class.

    I got the idea to check that from this thread:

    https://support.searchandfilter.com/forums/topic/pagination-issue-when-going-to-page-2/

    Ross Moderator
    #19980

    Thanks for the update Kevin 🙂

Viewing 6 posts – 11 through 16 (of 16 total)

Search & Filter Support
Privacy Overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.

We also use cookies to store items in your cart as well as allowing your to login on the site.

You can adjust all of your cookie settings by navigating the tabs on the left hand side.

By continuing to use this site, you also agree to our Privacy Policy.