Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
tree: 1e3c78923b
Fetching contributors…

Cannot retrieve contributors at this time

70 lines (47 sloc) 3.376 kb

Exitwp (modified by Boris Smus http//:smus.com for Hyde)

Exitwp is tool for making migration from one or more wordpress blogs to the hyde blog engine as easy as possible.

By default it will try to convert as much information as possible from wordpress but can also be told to filter the amount of data it converts.

The latest version of these docs should always be available at https://github.com/thomasf/exitwp

Getting started

  • Download or clone using git clone https://thomasf@github.com/thomasf/exitwp.git
  • Export one or more wordpress blogs using the wordpress exporter under tools/export in wordpress admin.
  • Put all wordpress xml files in the wordpress-xml directory
  • Run the converter by typing python exitwp.py in the console from the directory of the unzipped archive
  • You should now have all the blogs converted into separate directories under the build directory

Runtime dependencies

  • Python 2.6
  • Pandoc : document conversion from html to markdown and so on... (haskell)
  • PyYAML : Reading configuration files and writing YAML headers (python)
  • Beautiful soup : Parsing and downloading of post images/attachments (python)

Installing non python dependencies in ubuntu/debian

sudo apt-get install pandoc

Installing python dependencies in ubuntu/debian

sudo apt-get install python-yaml python-beautifulsoup

Installing Python dependencies using python package installer (pip)

From the checked out root for this project, type:

sudo pip install --upgrade -r pip_requirements.txt

Note that PyYAML will require other packages to compile correctly under ubuntu/debian, these are installed by typing:

sudo apt-get install libyaml-dev python-dev build-essential

Configuration/Customization

See the configuration file for all configurable options.

Some things like custom handling of non standard post types is not fully configurable through the config file. You might have to modify the source code to add custom parsing behaviour.

Known issues

Near future improvements:
  • Target file names are some times less than optimal.
  • Rewriting of image/attachment links if they are downloaded
  • Meaningful translation/filtering of wikipedia publish statuses into something that usable within a fairly standard hyde setup.
Things I want to do to learn writing better python code:
  • Refactor code to use less nesting
  • Refactor code to use more try/except tests instead of if statements
Things that might be resolved later on if I find the time:
  • There will probably be issues when migrating non utf-8 encoded wordpress dump files (if they exist).
  • Integrate one or a few basic hyde site templates to render complete working hyde blog setups from wordpress exports.
Jump to Line
Something went wrong with that request. Please try again.