Updates and Changes

Most of the past year I have been so busy working on updates for me and my friends that I have had little time to post about my thoughts on the current state of the web, and technology. I apologize to my friends that have kept me in their feed readers! There have been so many changes in the world of tech that I am having trouble keeping up.

Some things I’d love to go into more detail one of these days.  Adobe abandoning flash for mobile devices, html 5 becoming the new standard, yet most are not being quick to embrace it, and why. Google axing it’s rss reader. My new tablet. WordPress good and bad. There is so much I want to go into.

I had planned on writing several posts today, but it has taken me so much longer to get my blog site back up and running on a new web server, that I am a bit more focused on wordpress today. I love WP, and have been a fan for years. I was happy with WP 1.5 – it worked just fine, and I would still be using it today if it was never updated beyond that. I like quick and clean, and wordpress has always been that for me.

Moving WordPress install to a new server – don’t forget these basic things

Lessons learned from exporting my blog today, and then setting up a new install of wordpress, then importing my original content.

My original version of wordpress for years had a blog roll / links section in the backend dashboard. A new install today has this functionality removed. You may want to copy your blogroll from your older version before you switch. I imagine there is a plugin out there to bring the blogroll back – I did like the original that gave the option to use a picture as the link. You can of course use the newer custom menus to do a basic text only blog roll, and add that widget to your sidebar if that’s all you needed. However this did not come through the export / import process that I had expected.

Permalinks – a new install does the dynamic post =?123 thing. I had forgotten to check what my exact permalinks were before the export, nameserver change, and then import. Good thing the internet’s way back machine / archive.org is there. My suggestion is go into your permalink settings and copy the structure while you still have you old blog setup up.

Plugins – which ones are you using? Make a list, these will not come over in an import / export of wordpress automatically. What I did was keep a tab open in firefox on my plugins page of my old web server. Once I had the new install up and running, I went to add my plugins, and simply clicked over to the tab showing what I had installed previously.

Plugin Settings!

The wayback machine, and having the plugins page open from my old web server was not enough to get my plugin settings back. I strongly suggest opening the settings for each plugin you have and making notes. I ended up finding some plugins that offer an export settings option, but one of those did not import the settings from itself to it’s new install. Copy and pasting some plugin notes into notepad saved me from screaming when it came time to adjust the post teaser plugin for one of my friends recently. Her all in one seo settings were lost however.


I keep a copy of my original site open in another tab, this lets me quickly add the widgets in the right places for the new install. Some widgets also have settings that you only see in the backend, so if you use some widgets that have settings, get those notes before you move your worpdress and it’s nameservers. Luckily for me it is basic widgets, and the order is not too important for me. I was surprised, as noted above, of the missing in action (no longer available) links / blogroll widget with this new install. A friend of mine had a widget that included settings for hiding pages from navigation, and images that would display in his link roll – those have all been lost.

Sorry goes out to Steven for losing his sidebar! If we really wanted to, we could switch the name servers back to his old host, wait for it to propagate, then go back in there and get these settings. Perhaps find a widget that will work like the old blogroll / links function wordpress deprecated. We might just pull the code and hand write the html into a text widget – not sure if he really wants to keep those links bad enough to warrant the extra 10 minutes of work though.

I hope some others will learn from these lessons I went through today.

Make notes of all your settings, get a full backup of your files, and your database. Simply having the the wordpress xml export is a great way to save your precious words, but it is not a complete backup of your site. Even if you were running the latest wordpress, moving to a new install will be different, and you will want to have as many notes about your settings for each one of the small parts that make this cms machine doe what it does so eloquently. This should especially be on the mind of developers who maintain WP installs for other clients.

It would be nice if a wordpress export would also include some other basic info – like the name of the theme you were using, the plugins that were activated at the time, what widgets you were using, what order, and any basic settings for the basic widgets would be a nice option. I don’t expect WP to export settings of the various third party apps. I have seen some others post about some better WP backup solutions – it may be time to seriously look into some of those, then test what would happen if a full server crash occurred, and we had to install a fresh WP on a new server, then import the backups.

Better to learn and test before a crash I can assure 110%.

1 comment

  1. Oh – and it would be nice if wordpress exported comment / discussion settings and other backend changes that would be nice to not have to remember after changing them years ago. Turning on and off comments, nested replies – all these things I do not believe made it via the import into a fresh install today. Ugh! Now what else did I forget to check?

Comments are closed.