[Mainsite/API] Incorrect chapter order with ascending sort

[Axilourous]

I noticed this on "Kouiu no Ga Ii", but I imagine it might affect other titles too. The chapters >24 and <30, when using ascending sort (the default), are displayed between chapters 21.6 and 22. The faulty sorting is almost entirely, but not quite, on volume lines; that is, all of volume six was put between volumes four and five, but so was 25-25.6, which is part of volume five. This problem does not appear to affect descending sort, the index, or the reader.

This also happens in Mihon, which uses the API, so I'm not sure whether this is a bug in the site or in the API.

---

Ignore this, original post (I am blind):

This only happens on "Kouiu no Ga Ii" as far as I've seen, so I'm wondering if this might not be a bug, but I can't see any chapters >24 and <30 by default. HOWEVER, if I reverse the sort order, sift through the index, use the reader, or enter via the corresponding forum page, I can access all the missing chapters perfectly fine. It happens whether I'm logged in or not, regardless of settings regarding hidden chapters or blocklists, and on both the main site and via Mihon.

I thought this was an API issue, because it affects my Mihon chapter listing as well, but when I manually make the request to the same endpoint that the extension does, it seems to work fine? None of these "missing" chapters claim to be unavailable or anything, either. Not sure what the discrepancy is...

The bug lies in this behavioural inconsistency, but I'm unsure whether the bug is that I'm supposed to be able to see these chapters or not.

 

[Atifus]

The chapters are still present in the usual sorting order (Descending), The bug has most likely something to do with the sorting since the Volume 6 appears (But does so before Volume which should not be the case)

Something similar was reported yesterday on the discord

 

[Axilourous]

I may be blind... I could've sworn it wasn't like that before 😭

Odd that they're in the correct order if I use ascending, but not descending. I wonder why chapter 25 and 25.X, which aren't in volume six, are affected as well.

Glad to know its just a sorting issue, though, and apologies for the duplicate report.

BTW, is this an API thing, or a site thing? I'd like to update the thread title to match the actual issue.

 

[Atifus]

I may be blind... I could've sworn it wasn't like that before 😭

Odd that they're in the correct order if I use ascending, but not descending. I wonder why chapter 25 and 25.X, which aren't in volume six, are affected as well.

Glad to know its just a sorting issue, though

I think they might be sorted by the last updated date (the last time the chapter was edited) which explains the chapters too...

and apologies for the duplicate report.

Not an issue, it wasn't posted on the forum

BTW, is this an API thing, or a site thing? I'd like to update the thread title to match the actual issue.

Its correct as is I'd say, the API response also sorts it wrong

 

[Axilourous]

A few observations.

First, it occurs to me that Mihon's "source" chapter ordering paints a new picture, since uploads aren't grouped by chapter number like they are on the main site's interface. In the app, all of the chapters are in order, except for chapters 22, 23, and 24 from "Yurii's Personal TraS(h)CAN" specifically.

Second, sorting the JSON output of /manga/{ID}/feed by updatedAt, these three chapters DO appear out of order, but between chapters 31 and 32, rather than 29.5 and 30. A lot of other chapters also appear out of order, which aren't out of order in the main site or Mihon. I can't find any response that'd put every chapter in the specific order I'm seeing in the interfaces I use. I assume there's more going on than just beng sorted by last update date.

Third, and somewhat off-topic, but I tried manually copying the Mihon extension's request as closely as I could based on the source code, and it puts the chapters in the correct order when I do it?? For reference, it sorts by both volume and chapter in descending order. Maybe I looked at the wrong part of the code 🤷.

I assume I'm missing something here, because none of this really makes sense to me, but hopefully it helps someone else. I'd be interested in seeing a request URI that actually produces the ordering we see in both the main site and Mihon app interfaces.