560 migrate drupal 7 comments #561
Open
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.
This PR addresses #560. I'm unclear if comments fall outside the scope of jekyll-import, but I personally found this solution helpful and effective.
These steps are not automated. The user must follow the steps at
script/drupal7-comment-migrator/0-README.md
, but all of the SQL and Python is provided for them.It is necessary to generate the node ID (called
nid
) in the front matter of each post file. This is what establishes the relationship between the node and its comment file, which would be found in_data/comments/yournodeid.yml
. So I updated jekyll-import's drupal importer to generate that.I also added some contribution instructions for ruby amateurs like myself. 😅
When finished, you'll end up with comments pulled into each post dynamically using Liquid include templates:
