mytest
eBooks, Books, and more from ARUDOU Debito (click on icon):
UPDATES ON TWITTER: arudoudebito
DEBITO.ORG PODCASTS on iTunes, subscribe free
“LIKE” US on Facebook at http://www.facebook.com/debitoorg
http://www.facebook.com/handbookimmigrants
https://www.facebook.com/JapaneseOnlyTheBook
https://www.facebook.com/BookInAppropriate
Hi Blog. As people have written to me several times over the past few days (thanks for the concern!), Debito.org was down for more than a day. This was not due to cyberattack, but rather my server host migrating things over to some new hardware, I’ve been told. While I find this explanation quite unsatisfactory (taking a day of downtime with no warning?), Debito.org is back up and seems to be running fine.
That said, it’s running on backup files they created that happen to be about six months old (boy, that’s ludicrous). This means that a lot of images that were evidentiary are now missing (such as the first two book link images above). I have reuploaded successfully those images on the not-blog parts of Debito.org, but when it comes to the Debito.org Blog, even after I have reuploaded images from the past six months into the WordPress folder, they aren’t displaying correctly for reasons unknown.
Needless to say, I have contacted my server and asked them to fix things. But if you find missing images on pages, please let us know below in the Comments Section with a link and we’ll get the server host on it.
Thanks very much for the support, and sorry for the downtime. Arudou Debito, Debito.org Site Administrator
2 comments on “BLOG BIZ: Debito.org temporarily down but not out, some images now missing”
Did you check the capitalization of your image files? Not just the file name but the extension as well? If the webpage references “Image.JPG” but your file name is “image.jpg” it won’t load. Just tryin’ to help.
— Of course. Thanks. The file names and html encoding all seem to square okay, just checked the Repeta lecture notes post where all files being equal, some loaded and some didn’t. Dunno why.
Very unprofessional of your provider. Even ignoring the lack of notification, using old backups for migrating servers in an age of rapidly updated content (e.g., blogs) borders on negligence. Glad there was no malice involved, at least.