Quote from Manick

I changed it to use a title (pop up) instead. If you re-edit the page it should update?

Thank you so much😊

Not sure if it's intended, but I can no longer see my unfulfilled [Request Change] submissions on the User CP.

As of a few minutes ago, chapter progress counters are no longer updating.

Clicking a number, nothing happens. After a while a popup comes up stating: "Error, the server seems to be down at the moment. Check your connection or please wait until the server comes back up. Sorry"

The rest of the site is still working as I was obviously able to post this.

Edit: It's working again now.

Quote from recon21

Not sure if it's intended, but I can no longer see my unfulfilled [Request Change] submissions on the User CP.

This wasn't intended ... my functional test for this API function was terrible. I fixed it and updated the test to not suck.

Quote from Koneko_Nyaa

As of a few minutes ago, chapter progress counters are no longer updating.

It might be a scaling issue. I added another web worker node and the API CPU usage has decreased a bit on the existing nodes. Let me know if it happens again.

Oh, so this might be intentional, but I just noticed that while, on mobile, you can see that a series is on a completed/reading list, you can't see what list it's on, if you have custom lists. And even the drop-down menu doesn't change once you add it, unlike on desktop, so you can't even suss it out. Is it possible to change this, so we can see the exact list?

Also, this is something very minor so no worries if not, but on mobile can we have our username in the sidebar link to our profile? It'd be super helpful (for me at least, haha).

Thanks!

Quote from Alimeru

So it turns out that if you have a manga set to 5 chapters read, then use the -5 button, the number of chapters read will be set to 0. This isn't possible if you use the -5 button on a manga that has been set to =/=5 chapters read. You also cannot use the Edit button to manually set this number to 0.

I personally don't mind this "bug", and unless it's causing any backend problems, I think it should be up for permanent implementation as others have suggested in the past that it would be nice to start the chapter count at 0 since some groups like to label releases (such as prologues) like that.

I just realized I commented this on the wrong thread (the API bug report one). You can delete my comment in the other thread since it's not relevant.

I'm not certain when this changed, but I think it's very recent. If I do a search on the tag dictionary, the results are only the tags that start with the entered text, while it used to give all tags containing that text. The API (/v1/categories/search) is giving the same results.

Is this an intentional change? Possibly for performance reasons?

It was for performance reasons... I'll try to see if I can do something about it, as others have complained.

I've updated the category searching ... Let me know if it works for you.

Edit: The reason it's complicated is that there is no categories "table". When you search for a category in the categories section, it's actually an aggregation query on the nested tags lists that are a part of each series entry (in elastic)... so there are some really bizarre aggregations / filtering going on to make it work.

Yes, that fixes the issue. Thank you. Hopefully you can find a good solution to the performance issues.

I was doing a category search today on mobile (specifically Demon Lord/King) and noticed that the page numbers were overflowing.

Screenshot of the issue.

I removed the "Previous Page" button on mobile ...

Thanks! But, unfortunately, it still overflows a bit once you get to the 10s in page numbers.

Screenshot

You must have a really small screen... I think that's the best I can do for now.