lfa-wordpress-import/README.rdoc

60 lines
2.2 KiB
Plaintext
Raw Normal View History

= Refinerycms-wordpress-import
This litte project is an importer for WordPress XML dumps into refinerycms(-blog).
2011-06-02 15:13:56 +00:00
So far, only blog-relevant data gets imported, I'm working on the cms pages part.
== Prerequisites
As refinerycms-wordpress-import is an addon for RefineryCMS, is shares the prerequisites with it.
So you'll first need a running installation of refinerycms and refinerycms-blog. Make sure
the site is running, all migrations are run and you created the first refinery user.
2011-06-02 15:13:56 +00:00
== Installation
As there is no official release out yet, just add this repos to your projects Gemfile:
gem 'refinerycms-wordpress-import', :git => 'git://github.com/mremolt/refinerycms-wordpress-import.git'
2011-06-02 15:13:56 +00:00
and run
bundle
2011-06-02 15:13:56 +00:00
== Usage
Importing the XML dump is done via 3 rake tasks:
rake wordpress:reset_blog
This one basically deletes all data from blog relevant tables (taggings, tags, blog_comments,
blog_categories, blog_posts, blog_categories_blog_posts).
Use this one first, if you want a clean import of your old blog.
rake wordpress:import_blog[file_name]
This one does all the heavy work of parsing the dump and importing the data into refinery tables.
The parameter is the path to the dump file. Got a report from a Mac user, that the ~
didn't work in the path. I'll have a look at it, but till then, don't use it please.
If you don't want to import draft posts, you can set the ENV variable ONLY_PUBLISHED to true:
rake wordpress:import_blog[file_name] ONLY_PUBLISHED=true
The task will then skip all posts that are not published.
rake wordpress:reset_and_import_blog[file_name]
2011-06-02 15:13:56 +00:00
This one combines the two previous tasks.
2011-06-02 15:13:56 +00:00
== Feedback
This is still a very new gem. It manages to import my own blog and a standard WordPress 3.1 dump with some sample posts.
The first feedback is quite good, so it seems, the gem doesn't eat the machines it is installed on.
2011-06-02 15:13:56 +00:00
If you want to help make it even more stable, please throw your own WP dumps against it
and see what happens. If you encounter any bugs, please file a bug report here on github.
A sample dump that breaks this gem would be really helpful in that case.
2011-06-02 15:13:56 +00:00
For extra karma, fork it, fix it yourself and send a pull request! ;-)