<?xml version="1.0" encoding="utf-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Migrating from Typo3 to&#160;WordPress</title>
	<atom:link href="http://bradt.ca/archives/migrating-from-typo3-to-wordpress/feed/" rel="self" type="application/rss+xml" />
	<link>http://bradt.ca/archives/migrating-from-typo3-to-wordpress/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=migrating-from-typo3-to-wordpress</link>
	<description>Independent web developer, web designer, and entrepreneur living in Halifax, Canada.</description>
	<lastBuildDate>Wed, 16 May 2012 01:30:59 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Fedir</title>
		<link>http://bradt.ca/archives/migrating-from-typo3-to-wordpress/comment-page-1/#comment-35950</link>
		<dc:creator>Fedir</dc:creator>
		<pubDate>Tue, 31 Jan 2012 20:47:47 +0000</pubDate>
		<guid isPermaLink="false">http://bradt.ca/?p=561#comment-35950</guid>
		<description>I like Wordpress too. Big community. Simple code.
The backend is too simple, TYPO3 offers more.
We need workflow for our customers. TYPO3 has one.</description>
		<content:encoded><![CDATA[<p>I like WordPress too. Big community. Simple code.<br />
The backend is too simple, TYPO3 offers more.<br />
We need workflow for our customers. TYPO3 has one.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Segedunum</title>
		<link>http://bradt.ca/archives/migrating-from-typo3-to-wordpress/comment-page-1/#comment-34701</link>
		<dc:creator>Segedunum</dc:creator>
		<pubDate>Thu, 20 Jan 2011 16:57:49 +0000</pubDate>
		<guid isPermaLink="false">http://bradt.ca/?p=561#comment-34701</guid>
		<description>Fortunately, I haven&#039;t been directly involved with Typo3 but I have seen in detail projects that use it. Seriously, it&#039;s the worst CMS I&#039;ve ever seen. What&#039;s even worse is the accusations that &quot;You don&#039;t know how to use it&quot; or the explanation &quot;It&#039;s an enterprise CMS&quot; when you point its problems - whatever that means. I don&#039;t know what&#039;s funnier - that or how awful Typo3 is.

Firstly, look at whether you need a CMS. Logging into a site doesn&#039;t require one. Secondly, look at basic systems like Wordpress or Drupal where you can get away with doing as little customisation as possible. If you need a system where you find yourself doing configuration and programming use something like Plone. That at least has a sane system underneath it in Zope and Python. Oh, and it also has a sane front-end that is standards compliant. Buying a system in is also an option.

There should never be any reason for any software to invent its own language. If you see something that has then it&#039;s trying to do something that is horrifically error prone and ultimately impossible - customise away a CMS. Implementing a language also has its own performance issues.

I haven&#039;t even touched on the deployment issues.......</description>
		<content:encoded><![CDATA[<p>Fortunately, I haven&#8217;t been directly involved with Typo3 but I have seen in detail projects that use it. Seriously, it&#8217;s the worst CMS I&#8217;ve ever seen. What&#8217;s even worse is the accusations that &#8220;You don&#8217;t know how to use it&#8221; or the explanation &#8220;It&#8217;s an enterprise CMS&#8221; when you point its problems &#8211; whatever that means. I don&#8217;t know what&#8217;s funnier &#8211; that or how awful Typo3 is.</p>
<p>Firstly, look at whether you need a CMS. Logging into a site doesn&#8217;t require one. Secondly, look at basic systems like WordPress or Drupal where you can get away with doing as little customisation as possible. If you need a system where you find yourself doing configuration and programming use something like Plone. That at least has a sane system underneath it in Zope and Python. Oh, and it also has a sane front-end that is standards compliant. Buying a system in is also an option.</p>
<p>There should never be any reason for any software to invent its own language. If you see something that has then it&#8217;s trying to do something that is horrifically error prone and ultimately impossible &#8211; customise away a CMS. Implementing a language also has its own performance issues.</p>
<p>I haven&#8217;t even touched on the deployment issues&#8230;&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Max</title>
		<link>http://bradt.ca/archives/migrating-from-typo3-to-wordpress/comment-page-1/#comment-34664</link>
		<dc:creator>Max</dc:creator>
		<pubDate>Wed, 17 Nov 2010 09:20:12 +0000</pubDate>
		<guid isPermaLink="false">http://bradt.ca/?p=561#comment-34664</guid>
		<description>Typo3 is totally different with WP, if you try to turn Typo3 into a blog functions, it look like you using short-gun to kill an ant. Typo3 is a enterprise cms and Wp is a personal blog platform.</description>
		<content:encoded><![CDATA[<p>Typo3 is totally different with WP, if you try to turn Typo3 into a blog functions, it look like you using short-gun to kill an ant. Typo3 is a enterprise cms and Wp is a personal blog platform.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joshua Parker</title>
		<link>http://bradt.ca/archives/migrating-from-typo3-to-wordpress/comment-page-1/#comment-34256</link>
		<dc:creator>Joshua Parker</dc:creator>
		<pubDate>Sat, 11 Apr 2009 13:59:39 +0000</pubDate>
		<guid isPermaLink="false">http://bradt.ca/?p=561#comment-34256</guid>
		<description>Typo3 is a great piece of software. However, it is a framework, which is a different beast from Wordpress, Joomla, etc. Trying to turn Typo3 into a blogging tool is like trying to turn a tiger into a kitty cat.</description>
		<content:encoded><![CDATA[<p>Typo3 is a great piece of software. However, it is a framework, which is a different beast from WordPress, Joomla, etc. Trying to turn Typo3 into a blogging tool is like trying to turn a tiger into a kitty cat.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Beiträge von Typo3 in WordPress importieren - Beitrag - Schweizer WordPress Magazin</title>
		<link>http://bradt.ca/archives/migrating-from-typo3-to-wordpress/comment-page-1/#comment-34205</link>
		<dc:creator>Beiträge von Typo3 in WordPress importieren - Beitrag - Schweizer WordPress Magazin</dc:creator>
		<pubDate>Thu, 05 Feb 2009 15:48:54 +0000</pubDate>
		<guid isPermaLink="false">http://bradt.ca/?p=561#comment-34205</guid>
		<description>[...] auseinandergesetzt hat sich im letzten November Brad Touesnard, der sich zum Schluss mit einem selbstgeschriebenen Plugin zurecht fand. Zwar muss gesagt werden, dass das Plugin f&#252;r WordPress MU erstellt wurde, es [...]</description>
		<content:encoded><![CDATA[<p>[...] auseinandergesetzt hat sich im letzten November Brad Touesnard, der sich zum Schluss mit einem selbstgeschriebenen Plugin zurecht fand. Zwar muss gesagt werden, dass das Plugin f&uuml;r WordPress MU erstellt wurde, es [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Virgil Huston</title>
		<link>http://bradt.ca/archives/migrating-from-typo3-to-wordpress/comment-page-1/#comment-34203</link>
		<dc:creator>Virgil Huston</dc:creator>
		<pubDate>Wed, 04 Feb 2009 15:01:31 +0000</pubDate>
		<guid isPermaLink="false">http://bradt.ca/?p=561#comment-34203</guid>
		<description>There is the right tool for every job. TYPO3 has a big learning curve, one reason many people get frustrated with it. All enterprise level content management systems, open source or not, have steep learning curves. 

I use both TYPO3 and Wordpress. I settled on TYPO3 after months of research and kept concluding that it was the best in terms of feature sets, expandability, and enterprise capability. As for performance, many things can be done to MySQL, Apache, and TYPO3 to ensure optimum response. There are some huge sites using TYPO3 with great success.</description>
		<content:encoded><![CDATA[<p>There is the right tool for every job. TYPO3 has a big learning curve, one reason many people get frustrated with it. All enterprise level content management systems, open source or not, have steep learning curves. </p>
<p>I use both TYPO3 and WordPress. I settled on TYPO3 after months of research and kept concluding that it was the best in terms of feature sets, expandability, and enterprise capability. As for performance, many things can be done to MySQL, Apache, and TYPO3 to ensure optimum response. There are some huge sites using TYPO3 with great success.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Cannon</title>
		<link>http://bradt.ca/archives/migrating-from-typo3-to-wordpress/comment-page-1/#comment-34202</link>
		<dc:creator>Michael Cannon</dc:creator>
		<pubDate>Wed, 04 Feb 2009 12:52:44 +0000</pubDate>
		<guid isPermaLink="false">http://bradt.ca/?p=561#comment-34202</guid>
		<description>The SilverStripe URL should probably be http://silverstripe.org/silverstripe-cms. The other is the company website. SilverStripe definitely looks slick. 

For Acqal, most of our clients are coming to us specifically for TYPO3 as the tools they&#039;ve been using are too limited or want better qualified TYPO3 support.

I do keep an eye out for frameworks and CMSs to use as I do have my own &quot;I dislike TYPO3 days&quot;. However, with our enterprise needs clients, it&#039;s rare when TYPO3 isn&#039;t the right fit.</description>
		<content:encoded><![CDATA[<p>The SilverStripe URL should probably be <a href="http://silverstripe.org/silverstripe-cms" rel="nofollow">http://silverstripe.org/silverstripe-cms</a>. The other is the company website. SilverStripe definitely looks slick. </p>
<p>For Acqal, most of our clients are coming to us specifically for TYPO3 as the tools they&#8217;ve been using are too limited or want better qualified TYPO3 support.</p>
<p>I do keep an eye out for frameworks and CMSs to use as I do have my own &#8220;I dislike TYPO3 days&#8221;. However, with our enterprise needs clients, it&#8217;s rare when TYPO3 isn&#8217;t the right fit.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bradt</title>
		<link>http://bradt.ca/archives/migrating-from-typo3-to-wordpress/comment-page-1/#comment-34201</link>
		<dc:creator>bradt</dc:creator>
		<pubDate>Wed, 04 Feb 2009 12:44:25 +0000</pubDate>
		<guid isPermaLink="false">http://bradt.ca/?p=561#comment-34201</guid>
		<description>@Michael I certainly don&#039;t recommend Wordpress for every situation.  In fact, I&#039;ve just recently finished a project in which &lt;a href=&quot;http://www.silverstripe.com/&quot; rel=&quot;nofollow&quot;&gt;SilverStripe&lt;/a&gt; was used and it would have been a lot more work to use Wordpress.  You may want to check out SilverStripe. Thanks for your input!</description>
		<content:encoded><![CDATA[<p>@Michael I certainly don&#8217;t recommend WordPress for every situation.  In fact, I&#8217;ve just recently finished a project in which <a href="http://www.silverstripe.com/" rel="nofollow">SilverStripe</a> was used and it would have been a lot more work to use WordPress.  You may want to check out SilverStripe. Thanks for your input!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Cannon</title>
		<link>http://bradt.ca/archives/migrating-from-typo3-to-wordpress/comment-page-1/#comment-34200</link>
		<dc:creator>Michael Cannon</dc:creator>
		<pubDate>Wed, 04 Feb 2009 12:11:59 +0000</pubDate>
		<guid isPermaLink="false">http://bradt.ca/?p=561#comment-34200</guid>
		<description>Getting started with TYPO3 can be a bit of a pain, especially when there&#039;s been several different developers and no cohesion between what they&#039;ve been doing. 

However, if all you really need is a blogging tool and a system running out of the box, then Word Press is indeed a better tool than TYPO3. However, when you want to start involving more than 1 writer, multiple editors, multiple languages, automatic graphic generation, thousands of plugins, and a multiple tier structure; then TYPO3 is better than Word Press.

A blanket statement of X is better than Y, without Z reasons can be construed as an uneducated response.

In the end, use the right tool for the job.</description>
		<content:encoded><![CDATA[<p>Getting started with TYPO3 can be a bit of a pain, especially when there&#8217;s been several different developers and no cohesion between what they&#8217;ve been doing. </p>
<p>However, if all you really need is a blogging tool and a system running out of the box, then Word Press is indeed a better tool than TYPO3. However, when you want to start involving more than 1 writer, multiple editors, multiple languages, automatic graphic generation, thousands of plugins, and a multiple tier structure; then TYPO3 is better than Word Press.</p>
<p>A blanket statement of X is better than Y, without Z reasons can be construed as an uneducated response.</p>
<p>In the end, use the right tool for the job.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Migrating from Typo3 to WordPress :: WPLover</title>
		<link>http://bradt.ca/archives/migrating-from-typo3-to-wordpress/comment-page-1/#comment-34103</link>
		<dc:creator>Migrating from Typo3 to WordPress :: WPLover</dc:creator>
		<pubDate>Fri, 07 Nov 2008 00:33:37 +0000</pubDate>
		<guid isPermaLink="false">http://bradt.ca/?p=561#comment-34103</guid>
		<description>[...] wonder if anyone&#8217;s still using Typo3? This could be useful if you&#8217;re planning to migrate to WP. You can get a MU-specific plugin there, too, which may / may not work on plain vanilla WP, but at [...]</description>
		<content:encoded><![CDATA[<p>[...] wonder if anyone&#8217;s still using Typo3? This could be useful if you&#8217;re planning to migrate to WP. You can get a MU-specific plugin there, too, which may / may not work on plain vanilla WP, but at [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

