Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Hugo import from wordpress #100

Closed
spf13 opened this issue Oct 8, 2013 · 22 comments
Closed

Add Hugo import from wordpress #100

spf13 opened this issue Oct 8, 2013 · 22 comments

Comments

@spf13
Copy link
Contributor

spf13 commented Oct 8, 2013

'hugo import ....'

@danesparza
Copy link

Because hugo supports a markdown format, this might be similar to other Wordpress to octopress importers that I've used in the past. Something like this: https://gist.github.com/danesparza/5594888 (but in golang)

@robotamer
Copy link

There is a python script called exitwp that works like a charm.

https://github.com/thomasf/exitwp

@xaprb
Copy link

xaprb commented Dec 29, 2013

I have used https://github.com/benbalter/wordpress-to-jekyll-exporter and found it to work well.

@curioustechizen
Copy link

@xaprb Does that exporter add proper front matter so as to to retain the original URLs for the posts?

@adam-stokes
Copy link

@curioustechizen yea it adds a permalink item to the frontmatter

@JulienD
Copy link

JulienD commented Dec 28, 2014

+1 for ExitWP, I used it when I moved from WP to Octopress. It works like a charm

@rahul286
Copy link
Contributor

ExitWP is nice.

I used it many times with large WordPress sites with more than 5000 posts. No issues.

@anthonyfok
Copy link
Member

There is also a relatively new WordPress to Hugo Exporter, which works both as a WordPress plugin as as a PHP CLI script, which Cyrill Schumacher (@SchumacherFM) wrote based on the WordPress to Jekyll Exporter that @xaprb has used about a year ago:

It must be pretty good: A recent blog post by Jack Baty (@jackbaty) has nothing but praises for @SchumacherFM's great tool:

Converting from Wordpress was surprisingly easy. I used a plugin by Cyrill Schumacher and had all of my 1800+ posts, images, etc. converted for use with Hugo in less than an hour. All links were preserved so I don’t need to create a bunch of rewrite rules in Apache like every other time I’ve done this. Every step was easier than expected so I just kept going!

Moving forward, should we:

  1. considered this issue solved, maybe except documenting the existence of this wonderful WordPress plugin/CLI tool? Or...
  2. create a hugo import ... command that would fetch the WordPress to Hugo Exporter and guide the user to having it installed and run? Or, even more ambitiously...
  3. create a hugo import ... command which essentially does similar things as the PHP code, but all written in Go?

@adam-stokes
Copy link

@anthonyfok i like 1 for the path of least resistance. most people are probably used to checking the website for importers similar to what jekyll displays on their site.

@anthonyfok
Copy link
Member

Oh, one more thing: Jekyll does have its own WordPress importer:

as featured in http://www.smashingmagazine.com/2014/08/01/build-blog-jekyll-github-pages/

Though even in Jekyll's case, it seems that using the excellent WordPress to Jekyll Exporter by GitHub staff Ben Balter (@benbalter) is the recommended route.

@battlemidget: Good idea! Least amount of work for us, maybe perhaps writing a small tutorial. No need to reinvent the wheel, especially if WordPress to Hugo Exporter is already doing such a great job.

That said, if anyone really has the free time and really wants to do implement option 2 or option 3 as a Go programming exercise, I suppose that is welcome too. :-) But perhaps that time and energy is better spent on #101, a Jekyll-to-Hugo importer, as that no one has written yet.

Indeed, seeing that Jekyll Import already has the ability to convert from 23 other systems, we can leverage Jekyll Import to our advantage by perfecting our own Jekyll-to-Hugo Importer. Once that is done, we'll have the ability to convert from 24 systems, all for the price of 1! Haha! :-)

@bep
Copy link
Member

bep commented Jan 21, 2015

I couldn't get the "Wordpress to Hugo Exporter" to work. Issues with newer WP versions.

@SchumacherFM
Copy link
Contributor

I also don't use WordPress anymore ;-) and do not have the time to do further development on the converter script. If someone would like to have contributor permissions. Let me know.

@spf13 spf13 modified the milestones: v0.13, v0.14 Feb 22, 2015
@cgsmith
Copy link

cgsmith commented Apr 30, 2015

hey @SchumacherFM I'd be interested in contributing and getting it be similar to ExitWP. It would be nice to have it just parse the Wordpress XML or connect up from the local machine.

@SchumacherFM
Copy link
Contributor

Cool @cgsmith 👍
Send me first a PR if all looks fine and can be merged I may add you as a collaborator.

@anthonyfok
Copy link
Member

Status update:

@digitalcraftsman has kindly compiled a list of Hugo migration tools, and documented them at http://gohugo.io/tools/. See his Pull Request #1423 for more information.

Keeping this issue #100 open in case anyone wants to make WordPress-to-Hugo migration a built-in feature inside Hugo. 😉

@anthonyfok anthonyfok modified the milestones: future, v0.14 Sep 16, 2015
@michaelsync
Copy link

I got timeout error when I use hugo exporter. SchumacherFM/wordpress-to-hugo-exporter#8 ...

@Skarlso
Copy link
Contributor

Skarlso commented Jan 27, 2016

Hugo Exporter worked like a charm for me! However, there is a caveat.

Your URLs must be in the format 2016/01/21/name-of-your-post. This will help massively.

If the format is something like => ?p=123 it won't work well with Hugo.

@bep bep changed the title hugo import from wordpress Add Hugo import from wordpress Jul 21, 2016
@bep
Copy link
Member

bep commented Feb 28, 2017

This issue has been automatically marked as stale because it has not been commented on for at least four months.

The resources of the Hugo team are limited, and so we are asking for your help.

If this is a bug and you can still reproduce this error on the master branch, please reply with all of the information you have about it in order to keep the issue open.

If this is a feature request, and you feel that it is still valuable, please open a proposal at https://discuss.gohugo.io/.

This issue will automatically be closed in four months if no further activity occurs. Thank you for all your contributions.

@bep bep added the Stale label Feb 28, 2017
@bep
Copy link
Member

bep commented Mar 1, 2017

Note/Update: This issue is marked as stale, and I may have said something earlier about "opening a thread on the discussion forum". Please don't.

If this is a bug and you can still reproduce this error on the latest release or the master branch, please reply with all of the information you have about it in order to keep the issue open.

If this is a feature request, and you feel that it is still relevant and valuable, please tell us why.

@bep bep removed the Stale label Apr 9, 2017
@eklausme
Copy link

I have written a converter program in the Go programming language to migrate from WordPress to Hugo. This is described here: https://eklausmeier.wordpress.com/2017/04/24/converting-wordpress-export-file-to-hugo/

I am very much interested in seeing this as hugo import wordpress.

@stale
Copy link

stale bot commented Dec 6, 2017

This issue has been automatically marked as stale because it has not had recent activity. The resources of the Hugo team are limited, and so we are asking for your help.
If this is a bug and you can still reproduce this error on the master branch, please reply with all of the information you have about it in order to keep the issue open.
If this is a feature request, and you feel that it is still relevant and valuable, please tell us why.
This issue will automatically be closed in the near future if no further activity occurs. Thank you for all your contributions.

@stale stale bot added the Stale label Dec 6, 2017
@stale stale bot closed this as completed Dec 27, 2017
moorereason pushed a commit to moorereason/hugo that referenced this issue Sep 13, 2019
Do not prefix EnvName with HOOK_
@github-actions
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 11, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests