-
-
Notifications
You must be signed in to change notification settings - Fork 7.4k
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
Comments
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) |
There is a python script called exitwp that works like a charm. |
I have used https://github.com/benbalter/wordpress-to-jekyll-exporter and found it to work well. |
@xaprb Does that exporter add proper front matter so as to to retain the original URLs for the posts? |
@curioustechizen yea it adds a permalink item to the frontmatter |
+1 for ExitWP, I used it when I moved from WP to Octopress. It works like a charm |
ExitWP is nice. I used it many times with large WordPress sites with more than 5000 posts. No issues. |
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:
Moving forward, should we:
|
@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. |
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! :-) |
I couldn't get the "Wordpress to Hugo Exporter" to work. Issues with newer WP versions. |
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. |
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. |
Cool @cgsmith 👍 |
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. 😉 |
I got timeout error when I use hugo exporter. SchumacherFM/wordpress-to-hugo-exporter#8 ... |
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. |
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 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. |
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 If this is a feature request, and you feel that it is still relevant and valuable, please tell us why. |
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 |
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. |
Do not prefix EnvName with HOOK_
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. |
'hugo import ....'
The text was updated successfully, but these errors were encountered: