While developing our company’s blog I ran into some problems and roadblocks. Some have been due to WordPress itself and others due to implementing creative functionality like that sexy sidebar (post coming soon on that). I figured out how to correct and fix some of these issues by re-writing code, uploading to server, crossing my fingers, refreshing and then repeating those steps. Sometimes my prayers were answered, and when not I turned to Google and the great WordPress community. So now that I’m not having the development blues I’m going to do my part and share my issues and how I solved them over a series of posts.
First off I’m going to discuss the problems I ran into when backing up a database and moving it to our development environment. For those of you who have never backed up your wordpress database or attempted to switch it to a new wordpress blog on another server, you can get your basics from the documentation on the wordpress site here. So when I was duplicating our old blog database and install that resided at < www.creativemagma.com/blog > to have a new development stage at < www.creativemagma.com/cmblog > I ran into a problem with the database that I exported from the old blog. STOP, Let me make an important note, I did not implement a new or fresh installation of wordpress at < www.creativemagma.com/cmblog > I simply copied all files from < www.creativemagma.com/blog > and placed them in the < /cmblog > folder and changed the wp-config.php file to point to the new database. Once the old database was imported into the new database caused the new blog at < www.creativemagma.com/cmblog > to point all posts url’s to the old blog at < www.creativemagma.com/blog > I took a look at the newly imported database and I found my problems. When I browsed the wp_posts table I found two columns where I saw the old/wrong url.
Read the rest »