Skip to content

feat(multisrc): filter rearrangement to Novelphoenix - #2403

Open
52191314 wants to merge 1 commit into
lnreader:masterfrom
52191314:fix/novelphoenix-chapter-date-filter-rearrangement
Open

feat(multisrc): filter rearrangement to Novelphoenix#2403
52191314 wants to merge 1 commit into
lnreader:masterfrom
52191314:fix/novelphoenix-chapter-date-filter-rearrangement

Conversation

@52191314

@52191314 52191314 commented Aug 9, 2026

Copy link
Copy Markdown
Contributor
  • 'Sort Results By' and 'Translation Status' moved to the top of the filter list
  • bump novelphoenix to 1.0.1

Checklist

  • Update version code if an existing plugin was modified
  • Test changes in Plugin Playground or the app
  • Reference related issues in the PR body (e.g. Closes #xyz)

@52191314
52191314 force-pushed the fix/novelphoenix-chapter-date-filter-rearrangement branch from d22a892 to 22db19c Compare August 9, 2026 08:34
@MonomoySama

This comment was marked as spam.

@52191314

52191314 commented Aug 9, 2026

Copy link
Copy Markdown
Contributor Author

Can give the repo link? Gotta check to see if something broke. And btw, in your description, i see only 2 things, but didn't mention the default home page.... Upon opening the plugin, it should show the "Rank" page, but currently it's showing the "Newest Updates" page, which is the same page that shows up when clicking on "Latest" option beside the plugin AKA both clicking normally and clicking on latest goes to same "Newest Updates". You must change the default home page to RANK page

https://raw.githubusercontent.com/lnreader/lnreader-plugins/master/.dist/plugins.min.json
https://raw.githubusercontent.com/52191314/lnreader-plugins/master/.dist/plugins.min.json

It's the same link every time beside you have to change from lnreader to 52191314

@LordMonomoy

Copy link
Copy Markdown
Screenshot_2026-08-09-18-58-20-61 The filter option is still same... And the dates of chapters, they are stopping at chapter 2500 max, above that, all chapters are normal, no dates. I wonder if its coz of CF. If you find that it's indeed CF, then just remove the dates, no need to spend so much effort on it. It might make the code more messy and create problems Screenshot_2026-08-09-19-12-55-84

@LordMonomoy

Copy link
Copy Markdown

Ok i just did a migration, it was getting constant cf error, then i tried to update library, after the first novel, all other failed coz of cf block. Indeed, that upload date is causing this, coz i tried the 1.0.0 ver, all went smoothly, no cf blocks. You either doing it a bit wrong or it's just inevitable

…me page

- 'Sort Results By' and 'Translation Status' moved to the top of the
  filter list
- default sort is rank-top (Ranked home page instead of Newest Updates)
- bump novelphoenix to 1.0.1
@52191314
52191314 force-pushed the fix/novelphoenix-chapter-date-filter-rearrangement branch from 22db19c to 47a55e5 Compare August 9, 2026 22:21
@52191314

52191314 commented Aug 9, 2026

Copy link
Copy Markdown
Contributor Author

Ok i just did a migration, it was getting constant cf error, then i tried to update library, after the first novel, all other failed coz of cf block. Indeed, that upload date is causing this, coz i tried the 1.0.0 ver, all went smoothly, no cf blocks. You either doing it a bit wrong or it's just inevitable

It is indeed CF. Even with UA, still get CF.

@LordMonomoy

Copy link
Copy Markdown

Ok i just did a migration, it was getting constant cf error, then i tried to update library, after the first novel, all other failed coz of cf block. Indeed, that upload date is causing this, coz i tried the 1.0.0 ver, all went smoothly, no cf blocks. You either doing it a bit wrong or it's just inevitable

It is indeed CF. Even with UA, still get CF.

Ok then remove dates and it'll be done

@52191314 52191314 changed the title feat(multisrc): add chapter upload dates and filter rearrangement to Novelphoenix feat(multisrc): filter rearrangement to Novelphoenix Aug 10, 2026
@LordMonomoy

Copy link
Copy Markdown

I see you changed the title, but no date feature removal?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants