No, I'm not moving, not yet anyway. But Lava is. She scored a domain name which describes her blog so perfectly, that she couldn't help but nab it up: HowISaveMoney.net. Now what are the odds that this domain would still be lying around?
Lava finally made the big step and “moved into her own place". Moving domains is always such a hassle, but there are a few things that make the process a little bit easier. I was the Administrator during this move and I must say it was a little bit involved, but I think I got it done.
The domain was purchase at 1and1.com. Why not NetSolutions, Yahoo, GoDaddy? Because they all have great promotional deals but then it's upward of $8 to renew every year. 1and1 has a nice flat rate of $5.99 every year.
The host remained the same, since this particular hosts allows up to 10 domains pointing to it. All the files are simply dumped in a different sub folder. I both love and hate the idea of one consolidated host. It's easier to manage: one login one set of administration and maintenance, cheaper than several different hosts. But if one sight goes down, they all go down. If a hacker gets into one, he damn well gets into all of them. The load on all of the sites is still very small and way under the allotted bandwidth limit. Most of them are blogs using WordPress and we all know what a small physical footprint WordPress leaves behind. If any one site seems to out grow things little family what it turns 18 or something, it will definitely be kicked out of the nest onto it's on hosting package.
Now this should be the simple part. You copy everything into the folder that is going to house your new blog. There are a few minor changes that you might need to make. Depending on your previous setup you may need to edit the .htaccess file and change the RewriteBase option. But I do think that WordPress will configure it for you when you set up your permalink stuff.
One change that is necessary is editing your wp_config.php file. If you're changing databases, you need to make the changes here. If you're not changing databases you still need to make the changes to the table prefix. I forgot to mention that we still need to keep the old database active (details to come later).
I've sort of been fighting it for a while now. I must say I've been stuck in the past and I apologize for that. I was stuck in the whole “It's gotta be less that 800 pixels” things. That's just a basic rule of accessibility, which I've carried from years ago. Back them a significant number of Internet surfers still had relatively small monitors and used the 800×600 resolution. Therefore, if you wanted your content accessible to the highest majority of visitors you had to ensure that your site can be viewed relatively well in at least 800 pixels. Although the number of visitors using this resolution was in the minority, it was still not small enough to ignore.
Now comes another problem. Rather a solution that causes a problem. Most people fixed this resolution issue by slapping on a fixed layout. Now fixed layouts have their pros and cons. The pros are, you know exactly how it will look every time. You know where every thing will be on the website. One major con, I experienced at a friend's house. He had just gotten a brand new 21” flat panel monitor and everything looked so crisp. After a couple hours of playing, Wolfenstein: Enemy Territory we were just browsing the Internet and I just asked him to check out my latest post at the time. When he did I was horrified. My beautiful fixed width 787 pixel layout, which looks just brilliant on my 17” at home, still looked brilliant here, but it was so bloody small. I mean the thing was tiny and scrolling took forever. Yeah, we would have had to scroll a lot on a smaller monitor but since we have this huge one, why should we. There was just so much wasted screen space it annoyed me. You could almost fit a whole other site right next to mine.