Import from WordPress eXtended RSS

[ghost]

From @HabariImporter on June 27, 2011 0:12

Initially reported by: @ayunyan as #TRAC796
this patch adds import feature from WordPress eXtended RSS to WPImport plugin.

Copied from original issue: habari/habari#44

[ghost]

From @HabariImporter on June 27, 2011 0:12

Author: @gsnedders
WXR is not XML. [http://comox.textdrive.com/pipermail/wp-hackers/2008-July/021076.html]

Also, if you really want to treat it as XML, you shouldn't use the MultiByte class at all: SimpleXML's output is always UTF-8, and we use UTF-8 ourselves. WXR also de-facto has to be UTF-8.

[ghost]

From @HabariImporter on June 27, 2011 0:12

Author: @bjohnson
Instead of having several ob_start() and ob_end() statements with short template sections in between, can you make separate template files, set some theme variables, and use $this->display( themefile )?

[ghost]

From @HabariImporter on June 27, 2011 0:12

Author: @ayunyan
no longer using MultiByte::convert. and template was separated.
but, because output of Theme class cannot be acquired directly, ob_start() is necessary.

[ghost]

From @HabariImporter on June 27, 2011 0:12

Ticket imported from Trac:
http://trac.habariproject.org/habari/ticket/796

[ghost]

From @ringmaster on August 1, 2011 14:28

No idea why I closed this. Errant click?

[ghost]

From @rick-c on February 12, 2013 23:40

Shouldn't this really be closed. It seems like plugin territory to me, unless it's going to be added as an option to the current wp importer in core.

[ghost]

From @michaeltwofish on February 13, 2013 0:12

Seems like it should be part of the existing importer.

[ghost]

From @rick-c on February 13, 2013 0:34

As a base then, the export plugin has a wxr exporter. This could be referred to in creating an importer

[ghost]

From @chrismeller on February 13, 2013 1:34

I added WXR to the export plugin upon request. It was actually remarkably
easy to do. Changing the import plugin to support it (as well as BlogML)
shouldn't be significantly more difficult.

On Tue, Feb 12, 2013 at 6:34 PM, Rick Cockrum [email protected]:

As a base then, the export plugin has a wxr exporter. This could be
referred to in creating an importer

—
Reply to this email directly or view it on GitHubhttps://github.com/habari/habari/issues/44#issuecomment-13468233.

[ghost]

From @ringmaster on February 13, 2013 1:36

Note that WXR in the native parser supports the non-conforming XML that WordPress produces. If a WXR importer relied on SimpleXML, which relies on valid XML, then it would only be able to import Habari-created WXR, and not WordPress-created WXR. This kind of defeats the point.

[ghost]

From @chrismeller on February 13, 2013 3:2

The only WXR Example I could find is pretty well formed and I'm too lazy to install WordPress and create enough fake content to provide a decent testbed.

I threw together a crappy WXR parser using DOM, if anyone wants to find a worse example of WXR and mess around.

[ghost]

From @chrismeller on February 13, 2013 3:20

Another WXR Example that's much more modern.

[ghost]

From @chrismeller on February 13, 2013 18:7

Since there was a patch attached (a couple, in fact), here is a link to the mirror of the original Trac bug.

[ghost]

From @liblfds on June 23, 2013 16:53

FInd here;

http://www.liblfds.org/liblfdsorg.wordpress.2013-06-23.xml

A ~700kb file of Wordpress WXR, aabout two years worth of posts.