<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Ryan Boswell &#187; movabletype</title>
	<atom:link href="http://ryanboswell.com/blog/tag/movabletype/feed/" rel="self" type="application/rss+xml" />
	<link>http://ryanboswell.com</link>
	<description></description>
	<lastBuildDate>Mon, 28 May 2012 18:50:31 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>Migrating to MovableType 5</title>
		<link>http://ryanboswell.com/blog/2010/01/08/migrating-to-movabletype-5/#utm_source=feed&#038;utm_medium=feed&#038;utm_campaign=feed</link>
		<comments>http://ryanboswell.com/blog/2010/01/08/migrating-to-movabletype-5/#comments</comments>
		<pubDate>Sat, 09 Jan 2010 01:41:10 +0000</pubDate>
		<dc:creator>Ryan Boswell</dc:creator>
				<category><![CDATA[Posts]]></category>
		<category><![CDATA[movabletype]]></category>
		<category><![CDATA[work]]></category>

		<guid isPermaLink="false">http://ryanboswell.com/?p=268</guid>
		<description><![CDATA[Very recently, MovableType 5 was released to the public, and it was a huge update in terms of the backend. Mainly, it was no longer solely a blog-engine like WordPress, but also included the ability to create a static website. Before you would need to tweak the templates and fields to create one of these, [...]]]></description>
			<content:encoded><![CDATA[<p>Very recently, <a href="http://movabletype.com">MovableType 5</a> was released to the public, and it was a huge update in terms of the backend. Mainly, it was no longer solely a blog-engine like WordPress, but also included the ability to create a static website. Before you would need to tweak the templates and fields to create one of these, but there would always be mentions of blog-related tools and sections in the interface that you would need to ignore or re-purpose. Now, you can just create a website, with &#8216;blogs&#8217; as sub-websites.</p>
<p>In my business, I run a single MT installation for several websites to ease maintenance (one of the few things I prefer about MT over WordPress, the ability to manage several websites or blogs in one installation), and I had tweaked the templates and what not to turn the &#8216;blogs&#8217; into static websites. The other day I decided to upgrade this installation to MT 5 and then migrate the &#8216;blogs&#8217; to &#8216;websites&#8217;. This proved to be quite a laborious process and I decided to give up after only the first one. I spent two hours copying and pasting pages and templates across the two, making sure everything was duplicated properly. I was resolved to try and find an easier way of completing the task for the remaining 4 websites, since I was not looking forward to spending another 8-10 hours of copy and paste. When I re-approached the problem earlier today, I finally figured out a few tricks that I thought I&#8217;d share with anyone that might want to migrate a large website or multiple websites.</p>
<p>For the templates, I thought I would be able to easily solve my problem by just exporting them into a theme and applying it to the new website, except every time I tried to export  them from one of the blogs, it would give me an error. Just to check, I tried exporting the theme for the blog I had already migrated to a website; it worked wonderfully. So I had to give up there, and I resolved myself to copy and paste for the templates.</p>
<p>The pages and assets were a bit easier, I spent a few minutes in phpMyAdmin and changed all of the blog_id fields from the old &#8216;blog&#8217; to the new &#8216;website&#8217;, this worked pretty well, except for the pages that I accidentally put into the wrong website. For those, I simply copied and pasted into new pages rather than trying to figure out which ones they were in the MySQL database (which probably wouldn&#8217;t have been too difficult in hindsight).</p>
<p>All in all, I spent about 4 hours today migrating, publishing, and checking to make sure everything worked right (and aside from a few hiccups, it did). So those are my notes on migrating from MT 4 to MT 5, hopefully I can help someone else avoid hours of pointless copy and paste in lieu of some database trickery, with a little copy and paste on the side.</p>
]]></content:encoded>
			<wfw:commentRss>http://ryanboswell.com/blog/2010/01/08/migrating-to-movabletype-5/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RyanBoswell.com Version 2.0</title>
		<link>http://ryanboswell.com/blog/2009/02/16/ryanboswell-com-version-2-0/#utm_source=feed&#038;utm_medium=feed&#038;utm_campaign=feed</link>
		<comments>http://ryanboswell.com/blog/2009/02/16/ryanboswell-com-version-2-0/#comments</comments>
		<pubDate>Tue, 17 Feb 2009 00:20:17 +0000</pubDate>
		<dc:creator>Ryan Boswell</dc:creator>
				<category><![CDATA[Posts]]></category>
		<category><![CDATA[action-streams]]></category>
		<category><![CDATA[facebook]]></category>
		<category><![CDATA[movabletype]]></category>
		<category><![CDATA[openid]]></category>
		<category><![CDATA[twitter]]></category>

		<guid isPermaLink="false">http://pri.ryanboswell.com/?p=95</guid>
		<description><![CDATA[As you may have noticed if you visit regularly, there&#8217;s a new design up. It&#8217;s pretty similar to the old version. Basically, this is a refresh of the original design, since I liked a lot of the elements in it. One of the most noticeable changes is the absence of a proper sidebar. The purpose [...]]]></description>
			<content:encoded><![CDATA[<p>As you may have noticed if you visit regularly, there&#8217;s a new design up. It&#8217;s pretty similar to the old version. Basically, this is a refresh of the original design, since I liked a lot of the elements in it. One of the most noticeable changes is the absence of a proper sidebar. The purpose for this is that all the important stuff was moved to the bottom of the page in three columns. I wanted to turn my content into two columns, and there just wasn&#8217;t room for a sidebar, so I tossed it. The main color has stayed blue, because it&#8217;s one of my favorite colors, and it needed to stay that way to stay in line with my <a href="http://ryanboswell.com/blog/2008/05/07/refocusing-my-websites/#utm_source=feed&amp;utm_medium=feed&amp;utm_campaign=feed">branding scheme</a>.</p>
<p><span id="more-95"></span><br />
A few other big things is the inclusion of my <a href="http://twitter.com/rboswell" target="_blank">Tweets</a> in the stream of my blog. I had been <a href="http://ryanboswell.com/blog/2008/10/26/cosmetic-changes/#utm_source=feed&amp;utm_medium=feed&amp;utm_campaign=feed">planning</a> to do this for a while, but ran into problems using the Action Streams plugin, so I finally decided to write my own script that would fetch my Tweets and stick them into my blog database. It does remove any tweet that begins with an @reply, so as not to clutter things too much. But there is still a problem, I tweet quite a bit more often than I write long-form posts such as this one, so it is very likely that most of my site will be home to my Tweets.<br />
With the redesign, I&#8217;m also moving my comments back to an in-house system rather than use Disqus. The migration was pretty simple since, well, no one commented on anything while I was using Disqus. In the future I will be working on the comments to allow people to login using OpenID, Facebook Connect, Friend Connect, and other identity services to authenticate their posts.</p>
]]></content:encoded>
			<wfw:commentRss>http://ryanboswell.com/blog/2009/02/16/ryanboswell-com-version-2-0/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

