Pagination is not working in Magento 2.3.5-p1

[danielhirst2]

OS: CentOS Linux release 7.7.1908 (Core)

Magento Version: 2.3.5-p1

MySQL Version: Percona Server (GPL), Release 10, Revision f446c04

PHP Version: 7.2.29

Hello All,

We have recently migrated from Magento 1.9.4.4 to Magento 2.3.3, then updated to Magento 2.3.5-p1. After searching in our catalog, we have noticed an issue - even with the majority of custom module disabled (the only active is a debug dev bar). We seem to be having issues with the Magento pagination showing all products, although this has been set to 15,30,45 in the back end for both grid and list. We have also tried with these values removed to allow magento to use its default values. This seems to be having the side effect of slowing our website down. How can we amend this?

[Manish Mittal]

Hello @danielhirst2 

Can you explore more about logs and errors which is generating on server level or magento logs too. Please check console error as well and share here in more details if there any error related to pagination. 

Thanks

[danielhirst2]

Hello Manish,, there

Last I looked there were no issues/PHP errors/reports relating to pagination, there are some unrelated layout xml issues around YotPo, but I am sure this would not effect pagination.

I do feel this may be related although i am pretty certain i disabled redis for caching? 2020/07/21 11:09:50 [error] 27404#0: *306756 connect() failed (111: Connection refused) while connecting to upstream, client: 51.219.109.58, server: staging.incontinencesupermarket.co.uk, request: "GET /for-men/pants-for-men?product_list_mode=list HTTP/2.0", upstream: "http://127.0.0.1:6081

[danielhirst2]

Ah this was just because i disabled varnish for my testing (had the backup upstream of php) - no resolution here

[Manish Mittal]

@danielhirst2 

Can you confirm that redis and varnish enabled now or working fine? please check redis keys too.

[danielhirst2]

@Manish MittalMay have found my issue - a custom module/widget I made for 2.3.2 just going some testing for it now - seemed i hade a construct in that i didnt need and used an incorrect extend

[Manish Mittal]

@danielhirst2 

are you going to disable it? try then it might work