Report Website Bugs Here!
-
@myskaros Thank you!
-
@myskaros Thank you. Now if volumes 23-37 can be un-expired in the beta app as well, that would be awesome :)
-
@legitpancake That should be fixed in the 1.0, whenever it gets approved.
-
I’m unable to access the site at all, just getting a message about an unexpected error. Using the Safari browser and Chrome on IOS
-
@hester2006 Are you on an older phone? Have you tried switching between WiFi/cellular? It's working fine for me on my iPhone.
-
I’m on my iPad on safari and having no problems.
-
@myskaros on an iPad, page starts to load, I see the page for a second and then I get a blank page except for the words ‘an unexpected error has occurred’. This happens on all pages except the forums. It started when I was reading last night, suddenly it said you are not authorised to read this, I tried logging in again and can’t view anything since. I tried clearing all website data but no joy
-
@hester2006 Have you tried on incognito, or turning off any browser extensions? I was able to log in with your account and access the website just fine, so it seems to be a problem specifically with your iPad.
-
Conflict between schedule on the Calendar page and Series page.
https://j-novel.club/v/full-clearing-another-world-under-a-goddess-with-zero-believers-volume-1
Calendar says it just got released. (That's where I snagged the link from.)
Series page says it gets released on the 3rd.
Currently the link gives a 404. (Fight! Yurika!)
a short while later
Yay!
Now everything matches up for a 12/03 release.JNC support for the win!
-
@weasalopes said in Report Website Bugs Here!:
Conflict between schedule on the Calendar page and Series page.
https://j-novel.club/v/full-clearing-another-world-under-a-goddess-with-zero-believers-volume-1
Calendar says it just got released. (That's where I snagged the link from.)
Series page says it gets released on the 3rd.
Currently the link gives a 404. (Fight! Yurika!)
a short while later
Yay!
Now everything matches up for a 12/03 release.JNC support for the win!
Hurg...
Back to showing a 12/02 release.
Still with a 404 from the Calendar page (Fight! Yurika!)
Except that if you go to your User Library it is there and fully downloadable.So it has been released, you just can't get to it from the Calendar page.
-
@weasalopes What's your time zone? IIRC ebooks come out at 1AM Eastern Time on the listed day, so that might just be the day before for your time zone. My calendar (in Eastern Time) is showing it first thing today, though the link is indeed throwing a 404.
-
@lisast The calendar adapts to the user’s local time zone.
-
@legitpancake said in Report Website Bugs Here!:
@lisast The calendar adapts to the user’s local time zone.
Yeah.
As @LegitPancake says, JNC shows things in relation to the users local time zone.
This can make things confusing for readers discussing things in different time zones if they don't specify time zones in their post.
But JNC does a simultaneous worldwide release when things go live; time zone doesn't matter in that regard.Bottom line is...
If it's live, it's live; if it isn't, it isn't.
Which makes the Calendar page link go to a 404 an oddity, to say the least.
Which it's still doing at this time.All your libraries are belong to us. | Those who do not read shall not eat.
Help me, Satomi-san. You're my only hope. | Fight! Yurika!
Croquettes, Baguettes, and Books, oh my! -
Hi, I’ve been unable to access the main site since yesterday, with any attempt resulting in “an unexpected error has occurred” message.
While most of my attempts have been on my iPhone (6s), when I tried my computer, I was also unable to log on with Safari (which is what I use as my iPhone browser), though I was successful with Firefox. However, when I tried Firefox on my iPhone, I got the same error message.
If someone could look into this issue, I’d really appreciate it.
-
@weasalopes There were some slug naming issues, everything should be working now!
-
@myskaros said in Report Website Bugs Here!:
@weasalopes There were some slug naming issues, everything should be working now!
Indeed, it's all good now.
Yay!
-
@aki_iokua said in Report Website Bugs Here!:
Hi, I’ve been unable to access the main site since yesterday, with any attempt resulting in “an unexpected error has occurred” message.
While most of my attempts have been on my iPhone (6s), when I tried my computer, I was also unable to log on with Safari (which is what I use as my iPhone browser), though I was successful with Firefox. However, when I tried Firefox on my iPhone, I got the same error message.
If someone could look into this issue, I’d really appreciate it.
Temp fix is the old.j-novel site.
But yeah, I’m having the same issue. The new site stopped working on my iPad Air, but works on my laptop and iPhone 12 pro.
-
@thehalfwit said in Report Website Bugs Here!:
@aki_iokua said in Report Website Bugs Here!:
Hi, I’ve been unable to access the main site since yesterday, with any attempt resulting in “an unexpected error has occurred” message.
While most of my attempts have been on my iPhone (6s), when I tried my computer, I was also unable to log on with Safari (which is what I use as my iPhone browser), though I was successful with Firefox. However, when I tried Firefox on my iPhone, I got the same error message.
If someone could look into this issue, I’d really appreciate it.
Temp fix is the old.j-novel site.
But yeah, I’m having the same issue. The new site stopped working on my iPad Air, but works on my laptop and iPhone 12 pro.
Having just migrated from a pre-Lollipop Android phone to an Android 10 device, and also dealing with multitudinous PC OSes over the years, that's sounding like it could be an OS and/or hardware incompatibility; if your device isn't new enough, it might not be up to running everything involved with the new site.
There's a limit to backward compatibility, and just what is the final straw and when it occurs, who knows? -
@weasalopes said in Report Website Bugs Here!:
Having just migrated from a pre-Lollipop Android phone to an Android 10 device, and also dealing with multitudinous PC OSes over the years, that's sounding like it could be an OS and/or hardware incompatibility; if your device isn't new enough, it might not be up to running everything involved with the new site.
There's a limit to backward compatibility, and just what is the final straw and when it occurs, who knows?I don’t know about the others experiencing the issue, but the new websites been working fine for months. Just quit working this week out of the blue on my older devices.
-
@thehalfwit said in Report Website Bugs Here!:
@weasalopes said in Report Website Bugs Here!:
Having just migrated from a pre-Lollipop Android phone to an Android 10 device, and also dealing with multitudinous PC OSes over the years, that's sounding like it could be an OS and/or hardware incompatibility; if your device isn't new enough, it might not be up to running everything involved with the new site.
There's a limit to backward compatibility, and just what is the final straw and when it occurs, who knows?I don’t know about the others experiencing the issue, but the new websites been working fine for months. Just quit working this week out of the blue on my older devices.
Determining what the older devices have in common would seem the thing to do, then.
"Have in common" as in the age of the OS, etc., so it could be seen if there's a common 'break point' between users experiencing this; if the OS is older than X, they're now having this problem kinda thing.
When did it cease working with the new web site? Is that also a common break point? (Did everyone have it start being a problem at the same time?)The new web site isn't static, after all; the underlying software continues being updated, so the 'when' of ceasing to work with older devices would seem relevant to troubleshooting.
I'm pretty sure JNC is using a platform developed by someone else, so that 'continues being updated' includes updates from outside JNC when they choose to accept a platform update.
My terminology may not be current, it's donkeys years since I was involved with programming, but you've got the possibility of HTML standards updates, updates to the platform JNC uses, updates JNC made themselves, all of which could be the final blow to the ability of an older device to handle the current site. The old site still being accessible to these older devices while the new one suddenly isn't, if it can be seen to have any commonality between those devices in regard to OS versions or some such stuff, you'd think that'd help figure out what's going on.
