Build the Business of Your Dreams

Welcome to the Cranking Widgets Blog. We exist to help you get more done by showing you ways to be more effective and let go of the stuff that doesn't make you awesome. Be sure to subscribe to our feed and follow us on Twitter here.

We’re Back!

By , on Saturday, September 29th, 2007

For a reasons I don’t know, I decided to upgrade WordPress (the software the drives this here blog) yesterday. Anybody in the software business knows that you don’t make any large changes (like big upgrades) on Friday because you don’t want to spend all weekend fixing it if (read ‘when’) it breaks.

Well, it broke. The site was down for quite some time (around 24 hours, I’d guess) due to a small glitch with the new WordPress and my webhost’s environment. Because of the nature of the error, it wasn’t something I could easily or effective debug. I was actually unsure how to proceed when it was magically fixed (presumably by my webhost’s staff).

So, all that is to say that we’re back up and running. Apologies to anybody who tried to get here, but couldn’t. See you soon!

If you enjoyed this post…

You'll love getting free and freeing updates when we post new articles.
Enter your email below:

Enjoy these related articles

Reactions

  • http://www.stardel.com/fiveacres/ Elaine

    I upgraded yesterday and was astonished by how smoothly it went. For once I had done the recommended backups and perhaps it had prophylactic effect.

  • http://www.mallosworld.co.uk/organize-it/ Spike

    I’m holding off on updating WordPress because my site has already been down 48 hrs this month because of various server problems, and I don’t want to spend any more time fixing things :) Other than that, is the new WordPress any good? ;)

    SpiKe
    Organize IT

  • http://blog.scottjelias.net Scott Elias

    I guess that answers the question for me of whether to attempt to upgrade…

  • http://brettkelly.org brett

    Well, it wasn’t really a WP issue, I don’t think. Based on the fact that it started working with zero involvement from me, I’d say it was a configuration problem with my webhost.

    So, I didn’t mean for this to be some sort of indictment on WP 2.3 – please don’t take it as such :)

Get Free Updates

Enter your email below to get free and freeing updates:

You can opt-out any time.
We don't do spam.

Popular Posts

Search the Site