Is Ghost 2.x supported?

[slaFFik]

Official WordPress plugin does NOT support Ghost 2.x. They require you to install Ghost 1.x, import from WordPress to Ghost 1.x, and after that migrate Ghost 1.x to Ghost 2.x.

What about this tool?
Does it convert wordpress.xml file to ghost-1.x.json or to ghost-2.x.json?

[jonhoo]

This tool was written 5 years ago, so it definitely creates files for Ghost 1.x. That said, I think supporting Ghost 2.x should just be a matter of changing the structure of the generated JSON a little. Probably behind a --ghost2 flag or something like that. I no longer use Wordpress or Ghost, but would be happy to review a PR :D

[slaFFik]

Then could you please update the readme to indicate that it's currently for Ghost 1.x only?

I'm not sure whether I will switch to Ghost or not (I'm too deep in WordPress) for at least one of my sites, but I will keep this issue in mind. I think I will update the tool to support Ghost 2.x if I decide to switch.

[Asitis]

I'm in need for this tool for Ghost 2 now. I'll guess I'll try to do said update. I'm a JS novice though.
But this is the closest I'm going to get to automate it, so I'll try! :)

[Asitis]

So. Getting started with that task, I exported new Ghost 2 data, and Ghost 1 data, compared them.

The main difference is a "db": [ ] key wrapping the whole json, and updating the "version" tag to "2.5.0".
The content imported. I'm now going through it to see what is broken and what not, but this might be easier then you'd think!

Edit: Right, the biggest issue is the mobiledoc part of the content, and the formatting therein. Onwards!

[y26805]

So. Getting started with that task, I exported new Ghost 2 data, and Ghost 1 data, compared them.

The main difference is a "db": [ ] key wrapping the whole json, and updating the "version" tag to "2.5.0".
The content imported. I'm now going through it to see what is broken and what not, but this might be easier then you'd think!

Edit: Right, the biggest issue is the mobiledoc part of the content, and the formatting therein. Onwards!

According to the official migration page the db wrapper block is optional. I am more concerned about the potential need of mapping fields to others (see this issue).
It's a pity that there's no official documentation on the difference in JSON structure between Ghost 1.x and 2.x...