1 | 2 | 3 | 4 | 5 | 6 | 7 |
Good News / Bad News
Hey there, Alacrity.
The good news is, I've finally gotten the admin team back into the database.
The bad news is the server's HDD is full again, causing the broken images and chat issues you're all experiencing now.
Luckily, there is a very nice coder named Alan from whom I'm hoping to get some help on this in relatively short order, but, when it comes right down to it, these are going to be stopgap efforts.
As things develop I hope to keep you guys posted, and, if I get my way, we will not have to worry about this issue long term.
That said, I very much hate that the site is being a giant poopface at us all and I sincerely apologize on its behalf.
Keep your chins up
Posted by Kit (#7244) on Apr 19, 2016
Server Issues - Continued
Honestly, I wish I had news. I don't. The admins on this site have no access to the part of the site that's malfunctioning. The company that owns the site won't return our messages - believe me - we are all much more frustrated than you are.
At this point, we've started exploring alternatives to our current system since - obviously - this is not working. We were just starting to get our feet under us as a community again and this has been a punch to the gut.
I see and understand the flagrant hostility you guys are throwing staff's way, but really, we are in this together. No one wants our corner of the internet to be shown the respect it deserves more than Ehm, Larth and I. We just ask that everyone keep your fingers crossed and know that we are doing everything we can to get our site back.
Here's to hope.
Posted by Kit (#7244) on Mar 15, 2016
Site Issues 2: Electric Boogaloo
Hey again, all.
As I'm sure everyone's noticed at this point, the site has reverted to last week's state of FUBAR. This means that many dog images aren't showing up, and trying to equip things throws error messages and breaks dog images if they had been displaying previously. The chatroom is also not working.
Right now we have access to the database, but not the server, and the server is the source of these problems. We've contacted the site owner again so hopefully some coders will be able to get access and figure out what's going on once and for all. We thought the problem was solved after last time.
For now though, it's a waiting game for all of us. Thank-you all for your continued patience.
Posted by Ehm (#93) on Feb 19, 2016