wpzz

Sorry, I’m working on local dev and can’t provide online testing. I think that it caused by your infiniteScroll path option is set to default .next element instead of .ct-pagination .next. so, if there is other element with classname next exists before the pagination, infiniteScroll will try to get next href from that element instead of .next in pagination.

For example:

<!-- element in my plugin -->
<scroll>
...
<button class="next">Next</button>
</scroll>
...
<div class="ct-pagination">
<a href="#" class="next"></a>
</div>

will caused js error in console:

core.js:257 InfiniteScroll unable to parse next link href: null
r.updateGetPathSelector @ core.js:257
r.updateGetPath @ core.js:200
r.create @ core.js:82
s @ core.js:50
a @ infinite-scroll.js:31
c @ helpers.js:31
(anonymous) @ helpers.js:96
Promise.then (async)
n @ helpers.js:95
core.js:86 Disabling InfiniteScroll

and it will working if I change my button to other classname, e.g. <button class="scroll-next">Next</button>.

sure, I can change my classname to prevent this error, but I think this is a bug of your theme you may want to fix as it has potential conflict with other plugins.

• This reply was modified 3 years, 3 months ago by wpzz.