



This maintenance message seems to only appears in webview, in a normal browser the site works normally. So then i came here.
Guys? please don't ignore me.
Sorry, can't fix what I can't access.
Error 1020 Access denied
The site always been region-restricted, i dont think that's the problem.
there must be a way to fix... also thanks for the feedback
@maz1no What he's saying is that because the site is region locked, that limits who can work on the problem. We need access to the site to figure out what the issue is: no access means no way to figure out the issue, which means no way to correct it.
Understood. I can help with something? I'm not a senior programmer but i need this extension working again. If it serves as proof, when I access the site through the webview, the site returns me with the advice that the site is in maintenance. However, he's not and that has been going for a week.
This bug only affects mangasproject, and not all mangas, from my testing, at least One Piece still works fine for some reason.
Also, Mangalivre, which comes with the mangasproject extension, seems to have the exact same content as mangasproject and is working without any problems that I could find. In fact, looking at some commits, the extension maintainer even points out the mangalivre site is just a mirror of mangasproject, but with licensed stuff.
So I recommend you to just migrate everything you have to mangalivre, at least temporarily, until mangasproject is fixed.
I will take a look and see if I can fix it. Meanwhile, you can use temporarily the MangaLivre catalogue as pointed out by @0klux.
@alessandrojean I took a look at their website by using a proxy. I think it's an issue with val readerSrc = document.select("script[src*=\"reader.min.js\"]") not having the token in all cases. Something for you to check anyway.
Probably they have changed how the reader works and how they do the request to get the chapter pages, updating the backend and frontend only in the MangaProject and not yet on MangaLivre. Anyway, I will take a look, thanks @SnakeDoc83.
Okay, apparently they have changed the script to reader.toon.min.js, so Jsoup will not find the element, resulting the error reported. However, the token it's still there. Tomorrow I will submit a PR fixing it.