Then ran the new txp import script, natch

2 – Looked at the results. Some problems:
- Categories were imported, but the posts were still Uncategorized
- Some formatting problems. Probably easily fixed.
- Because I too wanted the same post ID, I had to delete the About Page post, and I’m a bit concerned that may cause future problems.

3 – Saved WP DBs in case I decide to once again start over:
- Saved WPDB with all TxP tables:
mysqldump –opt -u NAME -pPW WPDB > wptxpdb.sql
- Deleted all the TxP tables from the WPDB. Then saved again:
mysqldump –opt -u NAME -pPW WPDB > wpdb.sql
- Sizes were interesting. Note the WPDB was much smaller:
7.6M Aug 2 19:48 txpdb.sql
459K Aug 2 20:45 wpdb.sql
8.0M Aug 2 20:28 wptxpdb.sql
Why? The Log table in TxP was huge.

Hi! I converted my TxP to WP today following the instructions here. Here are some notes:

1 – To install my TxP tables into the WP DB, I used the mysql command line tools. This included:
- Dump the TxP DB:
mysqldump –opt -u NAME -pPW TXPDB > txpdb.sql
- Import into WPDB:
mysql -u NAME -pPW WPDB wptxpdb.sql
- Deleted all the TxP tables from the WPDB. Then saved again:
mysqldump –opt -u NAME -pPW WPDB > wpdb.sql
- Sizes were interesting. Note the WPDB was much smaller:
7.6M Aug 2 19:48 txpdb.sql
459K Aug 2 20:45 wpdb.sql
8.0M Aug 2 20:28 wptxpdb.sql
Why? The Log table in TxP was huge.

4 – Several future tweaks lie ahead:
- Fix categories. Fix/adapt to static pages which I used in TxP too.
- Move away from image handling used by TxP which uses an images directory with odd substructure and names like 1.png etc. Go to a more human style of an image directory with real names. Do the same in WP unless there is an apparent reason not to.
- Lots of reformatting and figuring out the CSS/Theme approach.
- Lose Textile. As much as I love it, I want to stick with basics: very simple HTML with CSS/Themes doing the heavy lifting. The WP editor is fine.

5 – TxP vs WP
- Win-Win .. both are great. Different styles of communities, different approaches to admin panel. TxP way nicer in some ways, WP in others.
- I plan to stay more flexible so that I can move away from either WP & TxP toward other new engines. In particular, I’m fascinated with SSJS (Server Side Java Script). So I really want a good export/import strategy.
- Cloud: I’m using cloud computing (Amazon, Aptana, Google App Engine, …) so I’m hoping some of these adapt nicely to WP or the SSJS strategy.

6 – A GREAT BIG HUG for this very helpful conversion blog entry. You’ve made lots of folks very, very happy. God bless you.

1 – I’m thinking about migrating to WP from Txp. I have Textpattern 4.0.6 currently and would be converting to WordPress 2.7.1. Will the above instructions work for this particular combination?

2 – Are you glad you converted!? I’m doing so in order to help a community (http://sfcomplex.org/) use it, including building plugins. Txp has been fine for me, but I’m a pretty light user.

— Owen

It looks like post category conversions (lines around 590) are using assignment instead of comparisons. That is:

if($cat1 = get_catbynicename($Category1)) { $cats[1] = $cat1; }

instead of

if($cat1 == get_catbynicename($Category1)) { $cats[1] = $cat1; }

More importantly, $Category1 doesn’t seem to be assigned a value anywhere

Finally, HTML entities in posts, such as nice quotes (ex: ’) get lost somewhere in the conversion.

Subsequent to my last comment, I discovered that whilst all of the posts and comments seemed to have been imported from Textpattern to Wordpress successfully, I discovered that the comments had not been linked in correctly.

I had a friend knock up a script to resolve the problem and relink the comments to the correct posts just by matching text on the corresponding systems. Not sure why the original scrip had problems on my system and no doubt this can be fixed. In the meantime, I have pasted a copy of the script in one of the comments on my blog.

See http://kyber.co.uk/blog/textpattern-to-wordpress/

Why is your script not included in the standard package I ask myself given that, as predicted, the one included does nothing.