This repository has been archived by the owner on Jun 3, 2020. It is now read-only.
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.
Hi,
Thanks for Exitwp. I've used it for migrating my data from my (old) WordPress blog to Jekyll. ☺
My posts are in HTML, which is the default in WP. The migration ran smoothly, but I've noticed that Exitwp outputs the content of the posts as-is. Now, when manually editing HTML posts in WP one can omit
<p>
s and<br />
s and they are automatically added using thewpautop
PHP command; thus, all of the paragraphs and line breaks in Exitwp's output were not processed by the browser as such, since they were whitespaces.The pull request fixes this. Using this Python implementation of
wpautop
. It changes the default target format from Markdown to HTML, because the conversion to Markdown loses data (I think you might want to add a warning about this in the comment on target/output formats in the configuration file).Thanks,
Júda