Fix wordpress import, since the input format seems to have changed #19
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Merged jekyll/jekyll#910. Good catch! |
parkr
added a commit
that referenced
this pull request
Apr 1, 2013
Fix wordpress import, since the input format seems to have changed
parkr
added a commit
that referenced
this pull request
Apr 1, 2013
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The main "import" command method invokes the importer like this:
Since the wordpress importer expecting separate parameters for dbname, user, ..., the import mechanism broke. Note that this fix only works with a Jekyll version where jekyll/jekyll#910 has been applied, since the import command is completely broken for me otherwise.