Kristie McNealy, MD

Last week was packed full of web development, including setting up three brand new sites powered by WordPress. All of that went off without a hitch (once I figured out that the WordPress version offered by my host is several versions out of date and not widget compatible . . .), so last night I moved on to transferring one of our business sites over to WordPress as well.

That, of course, is where my troubles began. The site I was working on is NaturalWoodFloors.biz, and since we get requests for information and estimates off that site, I was trying my best not to kill it completely. I did my own WordPress 2.2.1 install, as I’ve done the last three times, and suddenly I get database errors when I run the install script. Thinking positively, I give OLM overnight to get the database accessible, but you guessed it, in the morning everything was still broken. After a call to tech support, and several hours waiting while they ran a script to “fix” my database, of course, nothing was fixed. So, I gave in and ran the install script from my host, and had to upgrade to the newest version manually.

After all that, you’d think it would be smooth sailing. So, I open the css file from the existing site to find the correct color hex codes, and realize that they are all wrong. Eventually I figure out what the problem is, when I’m just at the verge of throwing my mouse against the wall again. That’s probably a good enough reason to take a break and help Riley ride her bike, so I’m off for now!

Similar Posts:

• Welcome!
• Be The Match: Join the Marrow Registry
• Riley’s Reviews Goes Live
• What Will the New Year Bring?