I'd planned out my Memorial Day weekend well in advance. I worked double-time late into the night all week to make sure I didn't have a lot of editing to do, had washed and ironed and folded and put away every single bit of laundry days beforehand, and had decided not to bother cleaning the house because it's a losing battle anyway. My holiday weekend was going to be as relaxing as possible.
When I woke up Saturday morning, I discovered our website for S&L Editing was down.
It took a couple of hours to find out it was going to stay down, like, forever. The server it had been living on had been nuked to oblivion. (Figuratively, of course.) I needed a new host, fast. The good news is, when the site was first being set up, I'd saved copies of the copy I'd given the webmaster for each page. Sure, losing the blog and its archives was a blow (except I'd saved copies of every blog post, too) but overall, the site shouldn't be too hard to recreate.
Ha. Ha, I say!
First I had to find an inexpensive host, using a platform I was comfortable with. I scoped out Squarespace, Wix, GoDaddy, Bluehost, and Hostgator. I was sorely tempted to go with FatCow, because hey, cows. Ultimately, I went with iPage, who also hosts this very site you're on right now, mostly because the price was great and I'm already familiar with how to build with them.
I'd already lost the better part of the day researching these prices only to find there's no place like where my other website already was. But setting up the site itself was a piece of cake. I opened up my docs from the original site, copied, and pasted into the site pages. Hit "publish" within an hour. Easy peasy, right? I typed "slediting.com" into my browser to see how it looked.
It looked exactly like staceylongo.com.
I logged back on to iPage. Hit publish again. And again. Double- and triple-checked Domain Central. Nothing. S&L Editing continued to welcome visitors to all things Stacey Longo.
I contacted tech support. Silly me! I was publishing to the wrong directory. I fixed that, hit publish again, and went to the website.
My author photo was gone. Hooray! But the lovely images and text and fonts and layout I'd selected when crafting the site? Also gone! What now welcomed people on our professional editing business website was DOS-like text on a sea of solid blue screen.
My editing partner had been letting me vent to him throughout the day. He and technology are not friends, and he often has weird mishaps occur with his computer, phone . . . anything with a microchip, really—that leaves the technician trying to help him scratching their head and muttering, "I've never seen anything like this." So when I was texting screams to Rob, he jumped to the rescue. Listen, I've had a lot of experience with the technology gremlins. The best thing to do right now is let it sit for the night, he advised.
And he was right! When I woke up the next morning, S&L's new website was up and running! With pictures and frames and everything!
Of course, now staceylongo.com was advertising professional editing and proofreading services at reasonable rates.
I decided it could wait. This blog entry wasn't due until Friday, and I had all week to try and wrestle with it. I wanted to enjoy a stinking hotdog on Memorial Day.
The good news: it's fixed now. :) Many thanks to Prakruthi in tech support for making that happen.
When I woke up Saturday morning, I discovered our website for S&L Editing was down.
It took a couple of hours to find out it was going to stay down, like, forever. The server it had been living on had been nuked to oblivion. (Figuratively, of course.) I needed a new host, fast. The good news is, when the site was first being set up, I'd saved copies of the copy I'd given the webmaster for each page. Sure, losing the blog and its archives was a blow (except I'd saved copies of every blog post, too) but overall, the site shouldn't be too hard to recreate.
Ha. Ha, I say!
First I had to find an inexpensive host, using a platform I was comfortable with. I scoped out Squarespace, Wix, GoDaddy, Bluehost, and Hostgator. I was sorely tempted to go with FatCow, because hey, cows. Ultimately, I went with iPage, who also hosts this very site you're on right now, mostly because the price was great and I'm already familiar with how to build with them.
I'd already lost the better part of the day researching these prices only to find there's no place like where my other website already was. But setting up the site itself was a piece of cake. I opened up my docs from the original site, copied, and pasted into the site pages. Hit "publish" within an hour. Easy peasy, right? I typed "slediting.com" into my browser to see how it looked.
It looked exactly like staceylongo.com.
I logged back on to iPage. Hit publish again. And again. Double- and triple-checked Domain Central. Nothing. S&L Editing continued to welcome visitors to all things Stacey Longo.
I contacted tech support. Silly me! I was publishing to the wrong directory. I fixed that, hit publish again, and went to the website.
My author photo was gone. Hooray! But the lovely images and text and fonts and layout I'd selected when crafting the site? Also gone! What now welcomed people on our professional editing business website was DOS-like text on a sea of solid blue screen.
My editing partner had been letting me vent to him throughout the day. He and technology are not friends, and he often has weird mishaps occur with his computer, phone . . . anything with a microchip, really—that leaves the technician trying to help him scratching their head and muttering, "I've never seen anything like this." So when I was texting screams to Rob, he jumped to the rescue. Listen, I've had a lot of experience with the technology gremlins. The best thing to do right now is let it sit for the night, he advised.
And he was right! When I woke up the next morning, S&L's new website was up and running! With pictures and frames and everything!
Of course, now staceylongo.com was advertising professional editing and proofreading services at reasonable rates.
I decided it could wait. This blog entry wasn't due until Friday, and I had all week to try and wrestle with it. I wanted to enjoy a stinking hotdog on Memorial Day.
The good news: it's fixed now. :) Many thanks to Prakruthi in tech support for making that happen.
RSS Feed