Recent Submissions pagination is not reloading properly

[tantz001]

When browsing a collection with more than one page, advancing to another (next or previous) page does not work. The page indicator moves as expected, but the items on the page do not change. In addition, mousing over the items results in a 'flicker' as if some sort of mouseover event is being handled. A page refresh results in proper display. Tested on chrome, safari, edge, and firefox with the same results.

UPDATED DESCRIPTION (Based on comments below):
The problem seems to be in the "Recent Submissions" listing of a Collection. Pagination is not working properly as the second page is never loaded when clicking on next page.

How to reproduce:

• Find a Collection with more than one page of "Recent Submissions". For example, this collection on the demo site: https://dspace7-demo.atmire.com/collections/8ad84c46-bdf1-4558-9b90-5c43ff396980
• Click on page 2 (or next page). You will remain on the first page of items even though the screen looks to reload.
• If you click the reload button in your browser, you when then jump to the second page of items.

[tdonohue]

@tantz001 : Could you describe how to reproduce this? What do you mean by a "collection with more than one page"?

UPDATE: Oh, do you mean the "Recent Submissions" list pagination is broken on a Collection page? That seems to be the case on the demo site, for example: https://dspace7-demo.atmire.com/collections/8ad84c46-bdf1-4558-9b90-5c43ff396980

[tantz001]

No, sorry, I mean a collection with more than a page full of items. The behavior I see, when for example I go from page 1 to page 2 of such a collection, is that the page indicator moves, but the list of items remains the same -- with the added twist of the 'flicker'. A simple (browser) reload/refresh of the page results in the correct page of items. And yes, just like the url you included noted in your comment. Apologies if this is a known issue, I didn't notice it!

[tdonohue]

@tantz001 : I've updated the description & title of this ticket to better describe the bug. Thanks for locating it. In the future, as noted, please provide steps to reproduce the bug, including links to the demo site (if reproducible there). That makes it a ton easier on me to determine whether this bug is a duplicate or new bug. In this case, this appears to be a new bug.