Import from wordpress to ghost 2.0


#1

Hi,
I just moved from wordpress to ghost 2.0, i used the wordpress plugin to move my posts, but when i try to import them into ghost 2.0 i get

Please install Ghost 1.0, import the file and then update your blog to Ghost 2.0.
Visit https://docs.ghost.org/v1/docs/install or ask for help in our https://forum.ghost.org.

is there anyway around this, i really don’t want to go all though this install again to get my posts into ghost


#2

Eh, the other way is manually update your export to fit the ghost 2.0 import format. I’d say going through the install again might be quicker, unless you only have a few posts.

Just had a thought, but that involves you sharing your export with me. I can put up a ghost 1.x pretty easy, run the import, update, run the export and hand it over to you. But that includes trusting me with your data.

Maybe you can do it yourself, if you’re familiar with docker. It makes it really easy.

@Hannah I also sent him a private message with a link to a clean ghost blog version 1.25 that’s at the ready if he wants to use it (yeah I’m hosting it I know, not ideal). But yeah, yours might be a better solution perhaps!


#3

Hi @sean2932 I totally get that it is not ideal, we don’t currently have anyone to maintain the current WP exporter plugin, and so it is very far behind.

You can install 1.0 on your local machine with Ghost CLI ghost install local --v1 to do the import -> upgrade -> export dance.

This is the best option we have right now, but again, we get that it isn’t ideal and are working on a better option.


#5

Are you comfortable with Docker?
If so this will be easy. Let me know if I can help.


#6

Do you think you could do the same for me? Happy to send over my export file from Ghost V1.


#7

Hey, I can do that, I’ll send you a pm with instructions.


#8

Thank you!


#9

Love is in the air :slight_smile:


#10

Docker is making it happen haha. So easy.


#11

Hi @Jivebunny :slight_smile: can you send me the instructions too? pls :slight_smile:


#12

I’ll be glad to test the “how to” if someone wants to write it :slight_smile:


#13

It’s ready for you. Sending instructions now.


#14

You know docker I think, so I could give you the instructions that I give to people who need it, but that’s probably not what you are looking for?

Basically, I just run the following:

docker run --name my-ghost-blog d -p XXXX:2368 \
-e url=https://my-ghost-blog.com \
-e NODE_ENV=production \
-v /path/to/your/docker/ghost/my-ghost-blog:/var/lib/ghost/content \
--restart=always \
ghost:1-alpine

I run it with a reverse proxy jwilder/nginx, and the letsencryptcompanion for it. That way I can host it securely for them on my own domain. They log in, create admin account, import data, send me a notice and I run the same command (after throwing away the 1-alpine container), and the only thing I change is the last part:
ghost:alpine

But I’m not sure you’re looking for that?

PS: the only downside is I can do 5 secure domains a day because of letsencrypt limitations.


#15

That’s good @Jivebunny :slight_smile: . But I think it’s overkill to go with the jwilder/nginx setup. Just run things locally without a PROD URL.

  1. Locally, put your file (converted from WP) into /path/to/ghost/

From this docs (which I contributed), RUN:

docker run -d \
	--name some-ghost \
	-p 3001:2368 \
	-v /path/to/ghost/blog:/var/lib/ghost/content \
	ghost:1-alpine
  1. Go to http://localhost:3001
    Your content appears normal under Ghost V1. Yeah.

  2. Remove your container. RUN:

docker rm -f some-ghost
  1. Let’s upgrade to Ghost v2. RUN:
docker run -d \
	--name some-ghost \
	-p 3001:2368 \
	-v /path/to/ghost/blog:/var/lib/ghost/content \
	ghost:2-alpine
  1. Go to http://localhost:3001
    Your content appears normal under Ghost V2. Yeah.

  2. Now you’re ready to go! Copy your data into your PROD env and start Ghost V2. Et voilà!

Cheers!
Pascal


Do I need the dedicated box to test Ghost locally?
#16

@sean2932, please let us know if it’s working for you :slight_smile:


#17

Yeah, true, but I ran it for them so they could access it remotely. They’re not local to my server, nor does it seem they have a docker installation available.


#18

I see! For most people, I think the local solution will be the way to go :slight_smile:


#19

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.