Comments on: Export from WordPress

By: chat

chat — Thu, 30 Nov 2006 19:47:45 +0000

intresting text , Thanks!

By: sohbet

sohbet — Sat, 25 Nov 2006 08:22:31 +0000

Please feel free to delete my comment above, if in any way you felt it does not belong there. I was trying to be helpful in whatever way I could, is all. Thank you for the effort and time you spent on making this possible.

By: Don Lapre Lover

Don Lapre Lover — Tue, 21 Nov 2006 23:22:56 +0000

Thankd for the idea and plugin. I haven’t used WP that much so I am looking for new things all the time. Thanks.

Laura Don Lapre Lover http://www.lauraglydaband.com
laura@lauraglydaband.com

By: Morteza

Morteza — Thu, 05 Oct 2006 01:35:46 +0000

good site

By: vissu

vissu — Wed, 20 Sep 2006 04:21:37 +0000

great effort,be little more clear so that no one will get errors while using,thank you for your good job

By: Matt

Matt — Thu, 01 Jan 1970 00:00:00 +0000

… where did my linebreaks go? Ah well. Pretend there are bullets and paragraphs there. I’ll chalk it up to being tired or a glitch in the matrix.

By: Matt

Matt — Thu, 01 Jan 1970 00:00:00 +0000

Groovy! Carthik is working on a non-lossy export using XML. MT export is great for portability (it's a fairly widely supported format) but isn't ideal as a WP export because it doesn't support everything WP does. When Carthik finishes the XML version (it's definitely going to be in 1.3) it will export (and import) custom fields, category hierarchy, post status, timezones, geo info, etc etc... basically lossless, and since it's XML we can do the encoding right too.

Anyway, if you're interested in cleaning up the MT script here are a few suggestions. I can try to help with things but my time is tight at the moment (hence an export not being written already!):

I would leverage WP functions, ie the $wpdb database class and the template tags. No need to fill in DB stuff again
I would break it up from One Giant Query into a bunch of iterated smaller ones. I know this isn't traditionally the best approach but you're less likely to run into memory limits that way (and your query is pretty heavy)
Again with $wpdb, use the table name variables so people who use a different prefix than wp_

Hmm, I actually had more when I started typing this but it has slipped my mind. I'll be back later. You might consider putting this on the wiki or filing a bug so other people could also contribute to this. I believe Shelley at BB was working on something similar.

By: PapaScott

PapaScott — Thu, 01 Jan 1970 00:00:00 +0000

They’re back now. I had experimented with the new upstream version of MarkDown, and it was eating all the line breaks.

By: Carthik

Carthik — Thu, 01 Jan 1970 00:00:00 +0000

I had finished work on a similar script a while ago, but then I agreed with Matt when he said that given the problems with the MT export format, we should think of a reasonable lossless and easily managed format.

My hack, based off of the same base as you hack is here: http://blog.carthik.net/wpexportv2.phps

It just begins to use the $wpdb class. The mysql related queries in there need to be replaced with $wpdb queries, but one improvement you could use is to avoid having the user to fill in the db details.

By: Jim S

Jim S — Thu, 01 Jan 1970 00:00:00 +0000

one more question...

if I do use mutliple categories but don't really care if they output correctly, since it was only a WP experiment on my testblog (I've never used them on MT....), will the script break if I just don't fiddle with it and assume that it'll export the first category?