There are two ways of moving a WordPress site from one server to another.

One is to create a database, and then copy all files to the new server, point wp-config at the new database and copy the contents of the database across.  This is the simplest way and ideal if, for example you are switching hosts.

The other method is trickier, but a lot more efficient, creating a leaner and faster site.  I have just completed a transfer of Head Rambles using this method.

The first thing is to create a new blank database on the new server, using a spare domain name for access.  Then upload a fresh copy of WordPress and using its built in features, create a new WordPress site.  The new site should be set up with the same Title and Subtitle as the old site, but using the new domain.

Next, copy across the theme files from the old server.  In my case I did a fresh install of Weaver II and then copied over the little backup files.  Any specific image files [such as the Banner and any images in the sidebar] should be copied across also.

At this point the new site should look identical to the old, but contain no posts or pages.

In my case, I then backed up the old database but did it one table at a time.  I then imported into the new database the following tables – Posts, Postmeta, Comments, Commentmeta, Terms, Term_relationships, Term_taxonomy and Links.  If the new database has been set up with a different prefix from the old [for example, if the old was WP_ and the new one is NEW_] then before uploading the files to the database, open them in a text editor and do a simple search and replace.

Don’t forget to copy over a copy of wp-content/uploads.

Now is the time to transfer plugins.  The ideal is to upload fresh copies of each plugin to the new site.  This is the time to decide which plugins are really necessary and which ones can be dumped.  Be ruthless!

At this point the site should be running smoothly and be identical in all respects to the old, apart from the domain name.  Now is the time to test that all the plugins are functioning correctly and that the site is behaving itself.

The next part is the tricky part.

Shut down the old site for changes [for example, disable comments]. Take another backup of the Comments database tables [and Posts if that has changed].  Upload these to the new database.

Now point the domain to the new server.  While that is propagating, open up the Options table in the new database and change every instance of the temporary domain to the permanent domain.

Once the domain has switched and is pointing at the new server the job is complete.  You should now have a much leaner faster site.

In the case of Head Rambles, the database dropped in size from 54Mb to 32Mb and from 34 to 17 tables.  Average page load time dropped from 1.48 seconds to 0.66 seconds which is quite impressive?  The main losses were database entries from redundant plugins and trimming the Options table from 16,225 records to 276 [a saving of 4.7Mb!].

The only problem I had was in switching the domain, where a couple of DNS servers got locked up for some reason.  It meant the whole domain was dead for a while, but the wait and the trouble was worth it.

To be safe, I have kept the old site running but with a different domain name.  It is blanked out for the general public but I can access it, for example if I need to cross check settings or retrieve any logs.  Once I am happy that it is redundant it, and its bloated database can be scrapped.

I mentioned before that I had rejigged my three blogs to use Weaver II.

I am currently in the process of designing another (for a friend of a friend) and am once again using Weaver II.

It has become a real challenge to see just how far I can go without changing any code whatsoever in the core Weaver II files.  So far I am really impressed.

One of the big features is the ability to insert snippets of additional HTML, CSS or Javascript into parts of the site just by entering those snippets in at the Admin area. 

So far I have been able to add CSS animation, customise a plugin’s display and to layout a complete page using CSS.  The latter was done by entering the various blocks (DIVs) on the page itself and then using custom CSS to handle those blocks.

I did come across a couple of areas though where in the bad old days I would have modified the raw code.  In particular I wanted to be able to place my own code in specific areas on pages.  For example, I wanted to insert some additional text onto the Comment form and also some Javascript (for Google Ads) onto posts.  The way around this was to install another plugin – Code Insert Manager – which does exactly what I want.  I realise there are plugins for Google Ads, but the Insert Manager does this and a lot more besides.

So far, I have managed to do everything without any file editing with one small exception – I use the CKEditor plugin for WYSIWYG comment editing and I wanted to modify the available buttons.  This isn’t possible from the admin area so I finally had to resort to tweaking the plugin’s file.

Weaver II also has its own plugin (Weaver II Theme Extras) which is essential as it contains an excellent backup feature.  All non-default settings and code additions to Weaver II are backed up to a small file which can be stored locally.  In the event of catastrophic failure the entire site can be restored using the standard installation files and then retoring all the various modifications using the backup file.

That’s assuming you have a backup of the database and images, of course!

I started writing blogs back in 2006.

After a bit of searching at the time I found a template I liked, that was simple and easily adaptable, and have been using that template ever since.  In fact I started a second blog and used the same template (heavily modified) on that too.

Over the years, both the CSS and PHP files in the template were extensively modified, particularly as in the early days (pre-widget) I had hard coded a lot of items straight into the template files.

A couple of weeks ago I decided it was time for a bit of an overhaul.  The first thing I did was to “widgetise” Head Rambles.  That was fairly painless and the result looked almost identical to the original.  However I still had a load of modified template files and the CSS was in a bit of a mess.  I decided on a change of the core theme and template.

My good friend Kirk pointed me in the direction of Weaver II, which is a template he has been using.

My first impression was that it looked a bit daunting.  I set up a local server on my laptop and installed it there.  Sure enough, there was a bit of a learning curve.  The Admin area is quite large with a lot of options.

My first project was to create a theme to match the Rambles one as closely as possible.  The further I went the more impressed I became.  There is virtually no aspect of the design that couldn’t be changed from the Admin area.

Rambles is now running the new Weaver template and the original design.  The main aspect is that I haven’t touched a single PHP or CSS file so updates/upgrades won’t destroy anything.  As a bonus, I have been able to remove several plugins as their functions are built into Weaver. 

The only drawback, if you can call it that is that the theme is three times slower that the old one.  Does that sound bad?  If I say that the old one took 0.07 seconds to load while Weaver takes 0.2 seconds?  Not bad considering all the additional bonuses.  The new site is mobile friendly (previously I had to install a plugin and a clatter of extra themes).  It has a much better comment area, with nested comments.  And I can make any changes to the theme with a couple of clicks of the mouse, with no FTP or file editing at all.

Since then I have also redesigned this site and Smoking so all three sites are now updated.

I have a feeling I will be writing a bit more about Weaver!