Quote from Manick

Quote from q00u

As far as I know, React doesn't provide an event for when hydration completes, so I have no way of knowing inside my userscript when it's safe to update the page or not. I can put a delay, but it is impossible to know for SURE if I've waited long enough.

Googling tells me that there may be hacks to detect hydration completion with Mutation Observers, but I didn't look too deeply into it.

I haven't been able to find anything like that, unfortunately. 🙁

Is the hydration error occurring because you are changing the client side html before react is done hydrating?

Exactly. There is a known bug in react regarding mismatch errors firing off when anything is changed before hydration completes (still not fixed after two years; also, other frameworks don't seem to have this issue).

For reference, these are the userscripts I'm using:

• Add stars to new chapters
• Sort titles on reading list (not updated on github yet)

Would adding more predictable IDs to various elements help?

Not me, I've already converted over to the current system. But thanks for asking. They definitely were helpful on the old site.

Raised by wolves

Sorry for the delay in my response: It was not so much an app as it was an user script that you could add through tampermonkey, or similar, actually.

https://greasyfork.org/scripts/26513-mangaupdates-cover-preview/

It is the second such Usercript that I found, now that I recall, the first was simpler and was 100% dropped, this one I don't know if they will work on again. As of now it is unable to reach the data, and crashes at times.

Still, here is a capture of what it's doing now: https://files.catbox.moe/l9vmw5.png

edit: Hilariously, I found the thread in this very forum from which I got the scrip (both of them) and there is a comment from you from two years ago on it: https://www.mangaupdates.com/topic/rk51njs/i-made-a-cover-preview-userscript-p?page=3

Edit edit: I just realise that the topic kept going a lot more since my last post. That will teach me to be distracted for a week.

edit edit edit:

Quote from Moo-stly

My take on that script is working

Thanks a lot, I just saw this and added it. It works great.

I think I found an annoying bug. Sometimes when you +1 on a manga series, it won't register unless you stay on the page for a few seconds after clicking the +1 or +10 button.

I tested it by increasing the read number on a series and immediately closing the tab. After opening it again, the changes didn't save.

I remember there was a warning about this before the site update to the likes of "Your changes have not been saved. To stay on the page so that you can save your changes, click Cancel." I can't remember the exact message.

Quote from saitohgr

I think I found an annoying bug. Sometimes when you +1 on a manga series, it won't register unless you stay on the page for a few seconds after clicking the +1 or +10 button.

There was a 1 second delay in place before updates went through. I reduced it to 0.4 seconds. Let me know if that's better.

I remember there was a warning about this before the site update to the likes of "Your changes have not been saved. To stay on the page so that you can save your changes, click Cancel." I can't remember the exact message.

I don't remember this at all. I'll look into it.

Seems to be working well now, thank you.

Is the Release Date (old release) field broken? It keeps beings stuck on today´s date no matter what I try while submitting an old release.

I also read EU/US comics and am a librarian.
Manga-Masters, My ANN-Lists + Imdb

Quote from residentgrigo

Is the Release Date (old release) field broken? It keeps beings stuck on today´s date no matter what I try while submitting an old release.

Technically, that feature was never available to anyone other than admins. It's actually a bug that non-admins can see it. I'll talk to lambchops and we'll decide whether to modify the API to allow users to use it, or hide it as intended.

In the past, users would add a comment that says the old date, and an admin would modify it.

Hello! This is my first time posting in the forums, so hopefully I have the correct thread!

When I am signed out and search for a BL series, the cover photo does not display. Instead, there is a message: "You must login to see Hentai related images."

This is ONLY when signed out (ie using the site as a guest).

I looked up some series that are only tagged "shounen ai" for the genre and their cover photos show up. But any BL that is tagged "yaoi" as a genre, the cover photo doesn't display.

Here are some examples of the cover photo not showing (need to be signed out to see the Hentai-login message):

https://www.mangaupdates.com/series/mhukb1x/tonari-no-metaller-san

https://www.mangaupdates.com/series/zt2p7va/happy-of-the-end

https://www.mangaupdates.com/series/ryk4s22/yoru-to-asa-no-uta

And NONE of these are hentai, in case that wasn't clear. XD

Generally, Yaoi implies sexual content, so we hide the covers. Shounen Ai often focuses on the romance angle more.

I can't remember exactly why we blocked out the covers, but I think it had to do with getting delisted by popular search engines for having readily accessible explicit content. At some point, we started requiring covers to be edited to block out explicit content as well.

Oh, that's interesting! The covers weren't blocked out before the site update, so I just assumed it was something wrong with the update.

It's kind of strange that retailers can have those covers on their site and show up in search engines, though? And even be on shelves at Barnes & Noble with all the other manga. Like, everything that is licensed by English publishers and available through Amazon, Crunchyroll, Target, Barnes & Noble, etc. the covers aren't showing here on MU. Kind of weird to censor something that is allowed everywhere else, no?

Quote from DataGremlin

Oh, that's interesting! The covers weren't blocked out before the site update, so I just assumed it was something wrong with the update.

It's kind of strange that retailers can have those covers on their site and show up in search engines, though? And even be on shelves at Barnes & Noble with all the other manga. Like, everything that is licensed by English publishers and available through Amazon, Crunchyroll, Target, Barnes & Noble, etc. the covers aren't showing here on MU. Kind of weird to censor something that is allowed everywhere else, no?

I'm pretty sure we did it over a decade ago, possibly 15 years. It's possible that things have changed since then. We'd have to re-evaluate.

I dug through the trash on my phone and found some screenshots I took BEFORE the site update and they show the cover photos when signed out. Screenshots were taken 10/4. Here's a comparison: https://drive.google.com/file/d/1QoPW0LwN_P21Kyq-0Jm-E61-GA7cjJXO/view?usp=sharing

(Please ignore the scribbles on the top images, they are unrelated to the topic but the only screenshots I still have from before the site the update.)

Quote from DataGremlin

I dug through the trash on my phone and found some screenshots I took BEFORE the site update and they show the cover photos when signed out. Screenshots were taken 10/4. Here's a comparison: https://drive.google.com/file/d/1QoPW0LwN_P21Kyq-0Jm-E61-GA7cjJXO/view?usp=sharing

(Please ignore the scribbles on the top images, they are unrelated to the topic but the only screenshots I still have from before the site the update.)

This is resolved.

Thanks so much! I really appreciate it!

For some reason, the option for "Show all (Some hidden)" for manga categories does not work, it just resets the page on the manga page so I can't see what categories a manga has except for the ones already shown. I use safari on my phone, and even google but this issue is still there. However if I use opera gx on my computer, it works fine. Also whenever I open a manga, it says "An unexpected error occurred. Please try again. If this continues, please notify an administrator.". I can reload the page but every few seconds, it pops up again. Also I cannot add anything to my reading list, as it just shows "Something went wrong".