Do not work on Taxonomy terms views (Drupal 9.1.5)

Created on 24 March 2021, over 3 years ago
Updated 23 June 2023, about 1 year ago

Problem/Motivation

Infinite scroll do not work on Taxonomy Term views with Drupal 9.1.5.
It works with others views as "Content" for example.
I tried with simplytest.me on D8.9.13 and it's perfectly working.
It's not an Ajax problem as if I create an exposed sort criteria with Ajax in my view, it's working.
I have no custom twig or custom JS enable so you should be able to reproduce.

Steps to reproduce

- Install a D9.1.5
- Install the module / clear caches
- Create some taxonomy terms (for example 7)
- Create a view with "Show: Taxonomy terms" as View Settings and name it for example "TestView"
- Create a page with "Use a pager" and 5 items or less to display
- Configure the view pager : select Infinite scroll
- [OPTION 1] : in options select "Automatically Load Content"
- Configure to 5 items per page (depending on what you set before) and apply
- in "Advanced" set Use Ajax to "Yes" and save
- go to your /testview page : Infinite scroll is not working, nothing happens.

- [OPTION 2] : don't select "Automatically Load Content"
- Configure to 5 items per page (depending on what you set before) and apply
- in "Advanced" set Use Ajax to "Yes" and save
- go to the "Preview" part of the view, click on "Load More"
- An error appears (see attached image)
- go to your /testview page and click on "Load More" : the page is redirected to /testview?page=1

Proposed resolution

I haven't found a solution yet, any help would be very welcome.

Please tell me if you can't reproduce.

πŸ› Bug report
Status

Postponed: needs info

Version

1.0

Component

Code

Created by

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡©πŸ‡ͺGermany Anybody Porta Westfalica

    Is this still an issue with 2.0.x? If yes, please update the version and set the status active again with clear steps or (best) with a test showing what's broken.

    2.0.x is the active development branch.

    If nobody replies, we should assume this is fixed and close this issue outdated.

    Thanks!

Production build 0.69.0 2024