I think the review part of the website hasn't had the URL change? When you press "return" after writing a review it doesn't work any more.

Have the IDs for personal lists changed by the way, or has that always been a thing? A friend of mine reported that the links to my reading lists don't work any more and I realised the ID in the URL is different now.

I'm not sure if these problems are related to the API update but I didn't know where else to post.

I think the review part of the website hasn't had the URL change? When you press "return" after writing a review it doesn't work any more.

The reviews section has never been very popular, so it wasn't prioritized. For the "return" issue, what do you mean? I tried to add a review and hitting back worked fine.

Have the IDs for personal lists changed by the way, or has that always been a thing? A friend of mine reported that the links to my reading list ...

I fixed this so that the old IDs work for public lists.

Thanks for the fix!

Quote from Manick

The reviews section has never been very popular, so it wasn't prioritized. For the "return" issue, what do you mean? I tried to add a review and hitting back worked fine.

My bad I meant the comment section, I forgot we had an actual review section too (and now that I think about it I've never seen anyone use the review section except for FMA).

For example, I wrote a comment yesterday for Urami Koi, Koi, Urami Koi.. When I write a comment, I am taken to a new page with a return button:

https://imgur.com/EetwfA6

However the return link appears not to work, so instead it returns an error. The link I got in this case is: https://www.mangaupdates.com/series/7ogffy1&perpage=10&page=1#comment168359

EDIT: the link to the comment from reading lists also doesn't work so I think the URL formula has an error.

I agree #2 is probably the best.

The biggest issue for #1 for me is that would entails even more requests to the server which it would be best to avoid for stability and cost related issues on MU part.

I agree with you on #3.

I'm a bit curious by the way. Could you explain why the "latest chapter" on the reading list is not updated when a release is deleted ? Does the release still exists in the database and is just disabled ?

It should update. What series is it again? Edit: you posted the title on your previous post... I'll check it out

Edit 2: Looks like it says chapter 50 for me?

I fixed links when editing, in addition to the links on the user pages. Thanks for the report!

I noticed on the https://api.mangaupdates.com/v1/releases/search that in the docs it is able to retrieve the series image via metadata, but on actual request most of the information in the sample is not in the response.

sample response has these keys in metadata series:
series_id, title, url, description, image, type, year, bayesian_rating, rating_votes, genres, latest_chapter, rank, lat_updated, and admin

actual response has:
series_id, title, last_updated, last_updated, and admin

https://play.google.com/store/apps/details?id=hikaru.mangaupdates

Great work with new api, but I have 2 questions.

1. Why does the Series RSS return less info per item than the Latest Releases RSS? I think it would be more useful for Series RSS to have more info to match, or at least have individual items link back to the main series page.

2. Are there any plans for a curated latest releases rss feed? Or more specifically, an rss feed with only latest releases that appear in a specified list.

So the schema object we use for that response is one that has all those objects defined, but the actual API function only loads the specific fields. It was a tradeoff between managing dozens of different schema objects for essentially different "views" of the data.

When you're looking at search results that include metadata, they will usually be views with a subset of the data rather than the full object.

1. The link on the channel is a link to the series. Is that not working well? Also there isn't any less data versus the latest release rss, or at least there shouldn't be...

2. I'd have to think about it. Series RSS can be cached because it's the same for everyone. Individual list RSS would have a different scaling/caching challenge because it would be different for everyone. Every pull of the RSS would lead to another query. I also know that some people have massive lists with thousands of entries...

For example using My Divorced Crybaby Neighbour.

Series RSS:

Releases RSS:

Quote from Manick

It should update. What series is it again? Edit: you posted the title on your previous post... I'll check it out

Edit 2: Looks like it says chapter 50 for me?

It indeed says 50 but when you look at the releases there is no chapter 50 for the serie.
It was a fake April Fools release that someone removed rightfully.
But then the latest chapter stayed at 50.

So you want the date and the link added back?

I fixed it.. I'll try to figure out why it didn't automatically work.

Yes that would be great!

Thank you very much.