Report Website Bugs Here!
-
@harmlessdave I've seen things you people wouldn't believe. Pre-pub release events for weeks and months back in time from the present. I watched J-Novel Club accomplish the impossible by catching up to Japanese releases in record time... Time to die.
-
@harmlessdave I know you're in both threads, but for the sake of posterity, I have addressed the problem you described here.
-
The release calendar has been fixed! Sorry about the trouble!
-
Hm, that was weird. When I came to main page as usual and clicked on releases, I was only getting content from the second half of today onwards. When I hit refresh, suddenly all the releases for the month appeared. Using Chrome on PC.
-
@crey Just scroll up and you'll see what the problem was and that it was fixed yesterday.
-
@elexid Unfortunately, that volume isn't up for preorder yet and it was given a release date too early. Sorry about that!
-
Ran into an issue in Chrome where I couldn't see the very end of Magicmaster v3p4 even though it existed. I believe I usually use a font size one or two sizes down from default, changing the font size allowed me to read the end. I'm used to hitting the end and having to backtrack, this was a different issue where no matter how much I went back and forth, it would not display the last page.
-
JS:Trojan.Cryxos.1420 - TWO separate occurrences, both today, block by BitDfender on MacBook using Safari while reading Discommunication Ch. 4
*Update - Make that 6 occurrences now
*Update... again - We're up to 8 occurrences, WTF. I think it's time to leave, bye-bye
-
@boyishlygirlish They compress and encrypt the javascript for the manga reader, it's a false positive. I had the same issue myself before. I solved it by whitelisting the site for now.
-
@terabyte Thanks! I've never had this happen to me before on J-Novel so I was freaking out a bit since it was back-to-back. Thanks for clearing this up
-
I'm having a recurring issue with the novel reader on the website.
The last page of a part gets skipped over when I tap for the next page and I get the interstitial page that prompts me to go read the next part instead...
I was able to replicate the issue on Elf Bride volume 7 part 7, I reached the end after reading of 95% the part. Since it ended oddly, I tapped the left arrow to go back two pages and the right button to go forward one page. It showed 92% and 96% respectively. (Font family and don't sizes were consistent throughout the experience.)
I'm currently reading on a Kindle Fire HD 10 and the Brave Browser version 1.1.2 (Chromium version 75.0.3770.143).
Although the example I gave was for Elf Bride volume 7 part 7, I was able to replicate this problem on all Elf Bride volume 7 parts with the exception of part 8 (the last two pages for it are at 91% and 95%).
-
Maou-sama retry! I can't access part 8, it says "You've found the Not Found page! That's some talent you've got!"
-
It’s still the middle of the night for people working at JNC but it has been reported, it should be corrected soon.
-
Amagi Brilliant Park: Volume 7 isn't available to download, I get an error 500:
"ENOENT: no such file or directory, open '/home/deploy/ebooks/amagi-brilliant-park-volume-7.epub'"
I pre-purchased with a premium credit.
-
It has been fixed, you can download it now.
-
{"error":{"name":"Error","status":500,"message":"ENOENT: no such file or directory, open '/home/deploy/ebooks/otherside-picnic-volume-1.epub'","errno":-2,"code":"ENOENT","syscall":"open","path":"/home/deploy/ebooks/otherside-picnic-volume-1.epub"}}
It broke
-
Just purchased Middle-Aged Businessman, Arise in Another World! Volume 1 with credit and it didn't show up in my library to download😭 I wanna read my book
-
You should email Supoort@j-Novel.club
They will be able to both assist you directly and faster then just posting on the forums.
-
@otherworldadvent11223 If you were already in your account when you bought the book, you will have to do a refresh of the "My library" page for it to appear.
-
@otherworldadvent11223 I definitely see it as a book you own in your library on the backend, have you tried refreshing like SomeOldGuy suggested? Or logging out and back in?
