[Bug] MangaDex: ext setting content rating
See original GitHub issueDevice information
- Tachiyomi version: 0.10.12
- Android version: 10
Source information
- Name: Mangadex
- Extension version: 1.2.110
Steps to reproduce
- enable content rating (for example suggestive/ero/porn/all 3)
- browse dex (its filtered/working here)
- search manga that shouldnt be showed(for example input
hai
)
Expected behavior
only show manga with content rating enabled
Actual behavior
show manga with all content rating
Other details
filter in browse workig just fine
use this for example maybe, should only return 1 manga https://api.mangadex.org/manga?title=hai&contentRating[]=erotica
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
[Bug] MangaDex: ext setting content rating - Bountysource
Steps to reproduce · enable content rating (for example suggestive/ero/porn/all 3) · browse dex (its filtered/working here) · search manga that ...
Read more >MangaDex
Read manga online for free on MangaDex with no ads, high quality images and support scanlation groups!
Read more >The Top 9 Best Tachiyomi Manga Extensions - wikiHow
1. MangaDex is one of the most popular extensions. Tachiyomi users love MangaDex because it offers a huge selection of comics in multiple...
Read more >MobileMD - Mangadex client – Apps on Google Play
MoblieMD is an app where you can read comics and manga from Mangadex without using a browser. Its lighter than Tachiyomi in terms...
Read more >Certificate Error : r/mangadex - Reddit
That's the thing, the extension itself works fine, and when I go to the manga through mangabat from tachiyomi, it shows up as...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
no its a main app issue, if you search and the filters are matching “default filters” it doesn’t pass the filters to the search
closing in favor of #5584