tag:blog.infosauce.com,2005:Typo Typo 2006-10-26T21:36:44-07:00 Tim urn:uuid:2dea2f9a-51fd-4fe3-bd66-3373727aef7c 2006-02-08T07:51:00-08:00 2006-10-26T21:36:44-07:00

<p>First off, a quick reminder kids, always back-up your DB before updating.</p> <p>I somehow seemed to run amuck of &#8220;this bug&#8221;http://www.typosphere.org/trac/ticket/454, when updating typo, to see if I could get Movable Type <span class="caps">API</span> working again, to use <a href="http://www.wbloggar.com/index.php?itemid=129">w.bloggar</a> to make my next post, to have some control over the trackback ping to the article, since I don’t know the current status of trackbacks in Typo. Well maybe it would have been quicker to check on that…. Of course, then I’d still be stuck updating.</p> <p>Anyways, somehow I got a wedged update, and for a while it looked like all comments were going to be down the drain. As I’m busy working on actual paying projects, I had to leave our blog in limbo for a bit. Thankfully, a post to the existing ticket got a reply that made it quick in easy to fix. The answer was obvious – go comment out the parts of the migration that are failing (the problem was trying to re-add a column that already had been).</p>

<p>First off, a quick reminder kids, always back-up your DB before updating.</p> <p>I somehow seemed to run amuck of &#8220;this bug&#8221;http://www.typosphere.org/trac/ticket/454, when updating typo, to see if I could get Movable Type <span class="caps">API</span> working again, to use <a href="http://www.wbloggar.com/index.php?itemid=129">w.bloggar</a> to make my next post, to have some control over the trackback ping to the article, since I don’t know the current status of trackbacks in Typo. Well maybe it would have been quicker to check on that…. Of course, then I’d still be stuck updating.</p> <p>Anyways, somehow I got a wedged update, and for a while it looked like all comments were going to be down the drain. As I’m busy working on actual paying projects, I had to leave our blog in limbo for a bit. Thankfully, a post to the existing ticket got a reply that made it quick in easy to fix. The answer was obvious – go comment out the parts of the migration that are failing (the problem was trying to re-add a column that already had been).</p>