Since my old ASP based CMS does not work on my brand new Apache server, I really had to look for a new content management system. I know I have written about this topic several times ago, but I never could convince myself to switch. Mainly because of the great amount of work. But now it is kinda urgent.
So I once again had a look at several CMS, including Textpattern, WordPress, Drupal, Typo3 and last but not least ExpressionEngine. Actually I was not that impressed by Drupal and Typo3 - mainly because of their administrative UIs. So that was the easy part. Choosing from the remaining three CMS was the though part.
But in the end I decided to go with Expression Engine, mainly because of its convenient way of handling multiple weblogs, its templating system and the possibility to easily integrate a forum module. Fortunately Veerle recently posted several great articles on setting up EE as well as on creating templates. Thanks :)
Even though I had a good start, I have one major worry: how to get all the old articles into the new CMS. That’s gonna be tricky. One possibility is to start from scratch and leave the old site untouched. Alternatively I could try to write some SQL scripts. Hm, I have to think about that. What do you suggest? By the way if you know any other great ressources on EE please let me know.
26 comments so far
Skip to comment form
Mackie September 10, 2006 at 12:44 AM
Personally I use TextPattern and like it a lot, but Expression Engine is also great. TXP doesn’t support having a forum.
As for transferring the entries the best way is to copy and paste them over, as I did when I switched to TXP. You could write a script to transfer it, but I’m not sure it will work with ASP, and the most it could take is 60…90 minutes.
Wolfgang September 10, 2006 at 12:49 AM
Well I can imagine transferring the showroom and articles section manually. But I have more than 300 weblog entries and thousands of forum posts and comments. That would take much longer than 90 minutes ;)
Martin September 10, 2006 at 02:34 AM
Ich bin von Textpattern zu EE gewechselt und habe die Artikel in das Link MovableType-Import Format exportiert und dann in EE importiert. Das geht schnell, klappt problemlos (solange beides UTF8) und man ärgert sich nicht mit der Datenbank rum.
alex September 10, 2006 at 04:26 AM
I have been using EE for quite some time now — on multiple projects, both personal and for clients — and I am quite happy with it. My biggest worry though was and still is, that there ist still no good tagging solution available for it (any hints anybody?). I have also noticed that they have started to more and more make it into an enterprise solution lateley (with forum , wiki and now e-commerce modules — see the new 1.5) which suits me but why not add tagging?
Justin French September 10, 2006 at 05:52 AM
What database does the old ASP CMS use? I’ve done a few major data migrations for CMSs in my time, but fortunately, they were always on the same database platform — MySQL.
In that case, I simply grabbed the “posts” table and started changing column names, types and specifications on the old data directly, trying to keep as much of my existing content as possible intact.
So the “posts” table may have to be renamed “articles” and the “date” column may need to be renamed “created_at” and converted from a date to a datetime, and I might need to drop two columns and add a new one, etc.
I guess the summary is, if at all possible, transform the existing data’s structure to match the new CMS structure, rather than trying to import it with scripts or whatever.
Failing that, the key is dumping the old data into a format that the new system or database (MySQL?) can read (perhaps even CSV?) and then shaping the data until EE can accept it.
Jesse Bennett-Chamberlain September 10, 2006 at 06:42 AM
Good choice on going with EE, you won’t regret it Wolfgang.
Alex, I think there are 2 different modules available for tagging. One is called “keywords”, and can be found in the wiki or the forums, and the other is called “tags”, which I think solspace created (I could be wrong). A native solution would be nice though, you’re right.
Pat September 10, 2006 at 07:17 AM
You should have checked out Symphony (symphony21.com). 1.5 is just around the corner (already released to current purchasers; free for everyone else later on).
Instead of using a set template method it uses XSLT to transform XML data into xHTML, which is by far much more flexible and powerful than a proprietary templating system.
Also its use of customizable fields means you can have sections that don’t have dates, entry bodies, etc.
Sean Hayford O'Leary September 10, 2006 at 04:11 PM
Baa! What happened to WordPress?
Scott Mackenzie September 10, 2006 at 06:51 PM
Interesting… I’m on the search for a new blogging/management tool. I’m using Wordpress at the moment and find it fairly solid. Expression Engine sounds alot more flexible though.
Did you consider Mephisto? It may be a little too light though, because you manage multiple content types plus there aren’t many add ons at the moment.
Kevin September 11, 2006 at 02:28 AM
With my little backgound in db migration from Access, Mysql, Oracle to Mysql, Oracle, Sybase for clients
Here is what I’d do : – dump existing database in flat files (csv, fixed length …) – create temp tables (same structure as source) – write some code (format, etc..) and rules (what to keep and when) to load selected data in the temp tables (.ctl files > sqlloader > .bad files | or php ?) – write some advanced transformation code (PLSQL, php?) to load in the target tables – drop the temp tables – replay it if needed
Jeremy September 11, 2006 at 09:24 AM
In fact TYPO3 is a great CMS, but unless you are already an advanced user, it’s too big and rough to manage a “simple” blog.
It’s an enterprise-level CMS, capable of all blog features, but so many others that it’s very difficult to get into it in less than a few month.
As a web developper, I’m using TYPO3 for many big web sites, but also Wordpress for blogs and smaller web sites. If you have to make a webzine, SPIP (a french – multi-lingual – product) is a must-try.
Martin Labuschin September 11, 2006 at 09:53 AM
You’ve already told us about your satisfaction with Wordpress… So, what’s your opinion about Wordpress.
I use Wordpress for a (almost) secrect project an i’m really impressed by this software. It’s standard-compliant and very extensible.
Chris September 11, 2006 at 10:20 AM
EE has MoveableType importer, so if you can figure out a way to export your old entries into MT format, it will be a snap to import them all.
More info on importing from other CMSes here: LinkToEE/
Chris September 11, 2006 at 10:21 AM
Ugh. The EE Wiki link above is broken. The last part of the URL should be “MigrateToEE”.
WD Milner September 11, 2006 at 03:38 PM
Actually there is a plugin for Textpattern to integrate PunBB. Someone has also shown on the Textpattern forums how to use Textpattern itself to implement a basic forum. EE is nice but I find its administrative interface rather convoluted.
Wolfgang September 11, 2006 at 10:00 PM
I’m also a big fan of WordPress — no doubt. But in case of my site I needed something more flexible to implement my journal, showroom, articles, sidenotes, links and the forum. However for a simple blog I would still stick by WordPress :)
Tim Adler September 12, 2006 at 04:23 AM
The problem with Wordpress is that you need a plugin for nearly any kind of special listing of content. Or if it is no plugin than it is at least a SQL-statement, which is avoidable.
I’m also using EE, and believe it is the CMS/Bloggin-software of choice. Since it simply offers the flexibility that one needs for a somewhat more personal solution for a blog, just like bartelme.at.
As for the importing of data, that will be difficult I believe. Cause EE is no way like Wordpress in that part. I think WP has like 8-9 standard-tables. EE on the contrary has like 30-40. I tried once to understand the way they organize, but gave up.
John September 12, 2006 at 07:50 AM
Nope. You simply need the standard-wp-function query_posts() to get the content you want. And with enough PHP-know-how, the need of using plugins is quite small.
Erika September 12, 2006 at 10:22 AM
I’ve been considering EE but I’m not sure yet. Let me know if you like it! Greetings from Brazil! Erika ;-)
Kevin September 12, 2006 at 10:45 AM
You need a standard intermediary. Why not using RSS ?
As far as I know, there are plugins to import posts via RSS. Am I wrong ?
Scott Mackenzie September 12, 2006 at 10:51 PM
I’m with Alex…. where’s the tagging support!?
Lincoln September 13, 2006 at 08:11 PM
Hi,
I’m a big fan of “Bartelme.at” a little bit shy but i’ve been visiting your site since long.
Compliments for choosing EE, i’m a “small” web desgner from Italy and have been using EE for a while, i can’t do without EE on any of my projects….
Nice Choice!!!
Wolfgang September 13, 2006 at 09:43 PM
Thanks. Yeah I’m also impressed of EE’s functionality and flexibility. I’ve already successfully converted some parts of the site. I even found a way to transfer my old data — I think I gonna use the MovableType import functionality.
Justin October 07, 2006 at 05:28 AM
just curious…but was the core version of EE enough for most of you or did you all spring for the $99 release?
Wolfgang October 07, 2006 at 06:04 PM
From my point of view the Core version fits the needs of almost every web site. However I chose the “Personal” version, mainly because of the Metaweblog API, the Query module as well as the Wiki module.
G. Wolfgang October 08, 2006 at 08:05 AM
What are your opinions on MODx, check http://www.modxcms.com, which I find to be an interesting and powerful CMS.