Report Website Bugs Here!
-
One thing I've noticed: When you attempt to buy/preorder a premium book (for instance this one), there's a small bug when you open the URL coming not directly from its title page: The text will show "Redeem a credit for ?" (emphasis mine) instead of the actual title ("Redeem a credit for Amagi Brilliant Park: Volume 3?").
-
-
I just bought Elf Bride volumes and when downloading them I noticed that volume 1 name still contains the world slave:
an-archdemon-s-dilemma-how-to-love-your-slave-elf-bride-volume-1.epub.I see also the redeem link still contains the word. Maybe you can't change it to not confuse the backend? Just nitpicking though.
-
@terabyte the series page on Amazon US also still has Slave in it.
-
The link for the latest lazy dungeon master release is https://j-novel.club/c/lazy-dungeon-master-volume-8-part-1 when it should be https://j-novel.club/c/lazy-dungeon-master-volume-4-part-1/.
-
This post is deleted! -
I have been having a problem with accessing "My Next Life as a Villainess: All Routes Lead to Doom!" and "Apparently it's My Fault That My Husband Has The Head of a Beast" chapters.
I can read all other series. I have cleared my cache and cookies and tried other browsers. If I completely switch to another computer I can read these series normally so I think the website must be blocking my home computer's IP address for these series.
-
I've let my membership expire until I can get assurances this long standing (over 3 weeks now) and several times reported issue is resolved.
-
I have been having a problem with accessing
That's not very specific, though that's understandable since web client isn't very specific about a lot of things.
If it's what I think it is you may get a better error message by going to network tab in browser's dev tools (Ctrl+I) opening part reader and looking at response to /partData request.
Edit: read your other posts and now I'm even more sure it's geolocation's fault. You can try mailing your ip address to support@ to maybe get the problem resolved. Can also try disabling IPv6 if it's on.
-
{"error":{"name":"Error","status":500,"message":"Part is not available in your country, JP"}}
Which is not true -- I am able to access the all of the other parts of other books normally -- it is only these two titles that will not allow me access (on my home machine). I remember right before the issue began I saw the same login that the Manga reader was giving for users who used a Google login for their membership... as I was already logged in I chose "cancel" and have never been able to read any parts of those books since (on this machine).
-
I am able to access the all of the other parts of other books normally
As Sam said in the other thread, only those two are geoblocked.
-
I am in Florida, not using any software to alter my geolocation so I can't see how this is an issue from my side.
-
@jason-maranto
No one implied it is. Geo-location services aren't that great in general and the one JNC apparently uses is extra bad.Also,
@_08 said in Report Website Bugs Here!:Edit: read your other posts and now I'm even more sure it's geolocation's fault. You can try mailing your ip address to support@ to maybe get the problem resolved. Can also try disabling IPv6 if it's on.
-
Email sent. We'll see if anything comes of it...
-
@_08 wait, really? I never remember him ever saying that.
-
@legitpancake Yeah. I recall Sam in Discord said a publisher required a geo-location block, too. (I don't recall which series, though.)
-
Just noticed that Werwolf series on the old announcement page still has the old/wrong name & cover: https://j-novel.club/announcements/5
(Slave) Elf Bride is wrong too.
-
@blanc-1 Submit a ticket to support with your email and Sam should be able to fix up your account 😉
-
I discovered that I can only view the Manga chapters if I login using my email and password. If I use login through Google, when I try to go to a chapter, it goes to a black page with a message in the middle that says I have be a subscriber, and to please log in.
-
@jeffrey-barrow Hi, I'm aware of this issue. I'll try and push a fix to the backend soon
EDIT: Fix imminent
