banner_jpg
Username/Email: Password:
News Article
Site Error Fixed
Some of you today probably noticed that accessing any series page gave an error, but only if you were a logged in user. Well, it's all fixed now~ Sorry for the downtime! (And in case you're wondering what happened, somehow the server cache got corrupted.)
Posted by lambchopsil on 
August 27th 4:39pm
Comments ( 15 )  
[ View ]  [ Add ]

Comments (limited to first 100 replies)

» Geese1 on August 27th, 2012, 4:53pm

Thanks for the fix!

thread

» forgottenone666 on August 27th, 2012, 5:25pm

Awesome job with the fix. Keep up the good work guys. biggrin

thread

» ultimatepunk on August 27th, 2012, 5:30pm

Thank you. :-)

thread

» toshirodragon on August 27th, 2012, 8:05pm

Oooops!

Yeah, I wondered what was going on there. Thanks for the fix!

thread

» calstine on August 27th, 2012, 8:10pm

Thank you!

thread

» Ustnap on August 27th, 2012, 9:02pm

Wonderful, now I can actually get back to looking at stuff again. smile

thread

» zenaku2005 on August 27th, 2012, 10:10pm

Thanks!

thread

» deadphoenix on August 27th, 2012, 11:34pm

Omg, it saved a lot, the most important info said suddenly sayonara. Well, now we can read new series again, thanks! smile wink grin

thread

» gonker on August 28th, 2012, 9:02am

thanks for the fix biggrin biggrin

thread

» beckyf98 on August 28th, 2012, 9:28am

Thanks!

thread

» Core Splendor on August 28th, 2012, 9:43am

Thanks! biggrin

thread

» VampireBanana on August 30th, 2012, 6:31pm

Hmmm thanks a lot for your hard work then! smile

thread

» stew00 on August 31st, 2012, 7:26pm

thanks alot, now if the content with security certificate errors is fixed, it really be back to normal

thread

» CrAzED on September 2nd, 2012, 9:30pm

Thanks for the fix. Did the error effect adding manga to wish list? Whenever I click Wish List or Reading List, nothing happens. Help? confused Nevermind it works in firefox just not chrome

thread

» lambchopsil on September 3rd, 2012, 2:09pm

Delete your cache and cookies and try again. It's something on your browser

thread