You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Pagination not working: Fails to load subsequent pages #2550
extension is not parsing the pagination from the source website.
Actual Behavior: Only the first page of novels/chapters loads in the app. The app does not load page 2, 3, etc., and there is no way to load more.
Expected Behavior: The extension should detect the "Next" button from the website and automatically load subsequent pages (infinite scroll) so all novels are visible.
Other Details
No response
Acknowledgements
I have searched existing issues and confirmed this is not a duplicate.
I have written a clear and descriptive title.
I understand that app-specific features should be requested in the app repository.
I have updated the app to the latest version 1.1.19.
I have provided all requested information in this form.
Just lining up the two reports so they do not contradict each other - both observations are correct, they exercise different paths:
The current release still ships "noPages": ["sort/most-popular"] for this source (see plugins/multisrc/readnovelfull/sources.json on master). With the default Most Popular browse, the plugin returns an empty list for page 2+ without sending any request at all, which is the "no way to load page 2, 3, etc." half of this report.
The other paths are unaffected: Latest-release browsing and the chapter lists work on 2.2.5, so the "works for me" check above can absolutely pass while the default browse stays broken.
The site does serve those listing pages: a local run earlier today (2026-09-22) fetched /sort/most-popular/2 and /3, each returning 20 distinct novels (none duplicated from page 1). A raw client hitting the site right now may instead get a Cloudflare challenge - runner/IP blocks are expected here and do not change the config finding above.
PR #2552 fixes exactly that line (drops noPages for sort/most-popular, bumps the version) and its checks are green.
Disclosure: this comment and PR #2552 are AI-authored (pi coding agent); nothing beyond the recorded checks above is claimed.
Activity
D3ICIDE commentedon Sep 22, 2026
Works for me check if your plugin version is 2.2.5
[
RibatTRW commentedon Sep 22, 2026
Just lining up the two reports so they do not contradict each other - both observations are correct, they exercise different paths:
"noPages": ["sort/most-popular"]for this source (seeplugins/multisrc/readnovelfull/sources.jsonon master). With the default Most Popular browse, the plugin returns an empty list for page 2+ without sending any request at all, which is the "no way to load page 2, 3, etc." half of this report./sort/most-popular/2and/3, each returning 20 distinct novels (none duplicated from page 1). A raw client hitting the site right now may instead get a Cloudflare challenge - runner/IP blocks are expected here and do not change the config finding above.PR #2552 fixes exactly that line (drops
noPagesforsort/most-popular, bumps the version) and its checks are green.Disclosure: this comment and PR #2552 are AI-authored (pi coding agent); nothing beyond the recorded checks above is claimed.