The following link (clicking to page 2 of the comments from the new expansion announcement) gives a Server Error (500):
Bugs
•
Posted by
MemeMachine
•
Created 6 years, 5 months ago
•
Updated 6 years, 4 months ago
•
Discussion
11 comments
507 views
Comments
The following link (clicking to page 2 of the comments from the new expansion announcement) gives a Server Error (500):
https://outof.cards/hearthstone/157-new-hearthstone-expansion-revealed-saviors-of-uldum-all-revealed-cards?page=2#comments
This page does the same (new Blackrock-Dalaran brawl):
https://outof.cards/hearthstone/158-dalaran-crashes-into-blackrock-mountain-blackrock-crash-brawl-rewards-old-seasonal-card-back?page=2#comments
edit: link
I'm not 100% sure but I think this bug appears every time there is a reply to a post that exists on a previous page.
dib is correct, currently theres a bug that causes this error when a comment with replies are split among different pages. It should be fixed soon, once a solution is devised. We certainly don't like it either
This should be fixed now (praise Flux!). If you still encounter issues with comments, please let us know!
I get a Server Error 500 when clicking any of the news from the front page or any deck (from front page as well as "Decks" section). Is it just me? Tried from home and work and different browsers, devices and cleared caches in between.
Edit: Nevermind, right after posting this everything started working fine again...
Hi, could you tell us what device and browser were you using? We are experiencing this bug again mostly on Chrome rn, will get it fixed hopefully soon, but more info is always good, thanks!
I had this issue this morning (Europe, between around 06:00 to 11:00 CEST). News Posts on the front page and pretty much all the links to decks lead to this error. The only section working was the forums. It occured on mobile (Safari) and desktop (chrome). Since about 12:00 CEST everything has been running smoothly.
I think iv identified the problem, or at least one part of it: you have to be logged in on the site, then no error. Obviously it shouldnt matter if you are logged in or not, we will have to fix that, but you can work around it this way for now, sorry for any inconvenience!
Late last night I pushed changes to the site to prepare us for site achievements. We were running a bad check when users were not logged in that has now been fixed.
Sorry for the trouble, look forward to some fun this week =)
Yes, exactly the same situation. Europe, Chrome on desktop or mobile Safari, about the same time span, and not logged in. But now it works again, regardless of being logged in or not.