WordPress import is improperly encoding HTML end tags

[richardtallent]

I just imported my Wordpress site (self-hosted) and all HTML end tags had the "/" replaced with "/", which of course makes them ever so slightly less useful as HTML end tags.

I commented the following line in wordpress.rb and it worked, but since I don't know the background of why this line was added in the first place (there must be a reason), I didn't want to send a naive pull request:

text.gsub!("/", "/")

Using the latest Jeckyll, jeckyll-import, Wordpress, etc.

[jekyllbot]

This issue has been automatically marked as stale because it has not been commented on for at least
one month.

The resources of the Jekyll team are limited, and so we are asking for your help.

If you can still reproduce this error on the 3.1-stable or master branch,
please reply with all of the information you have about it in order to keep the issue open.

If this is a feature request, please consider building it first as a plugin. Jekyll 3 introduced
hooks which provide convenient access points throughout
the Jekyll build pipeline whereby most needs can be fulfilled. If this is something that cannot be
built as a plugin, then please provide more information about why in order to keep this issue open.

Thank you for all your contributions.

[parkr]

@richardtallent Hey, this has been around ever since the beginning of this repo, which means it was in Jekyll proper before that (when importers were a part of the core repo).

Spelunking through history, that file was removed in jekyll/jekyll#793 Looking at the git blame for that file, it turns out @mattr- actually added that in jekyll/jekyll@8fb4e8f. He would be better suited to help you understand why it was added 😄

[jekyllbot]

This issue has been automatically marked as stale because it has not been commented on for at least two months.

The resources of the Jekyll team are limited, and so we are asking for your help.

If this is a bug and you can still reproduce this error on the master branch, please reply with all of the information you have about it in order to keep the issue open.

If this is a feature request, please consider whether it can be accomplished in another way. If it cannot, please elaborate on why it is core to this project and why you feel more than 80% of users would find this beneficial.

This issue will automatically be closed in two months if no further activity occurs. Thank you for all your contributions.

[richardtallent]

I haven't had a chance to look into Jekyll more until now. Reinstalled all the latest tooling, and I'm seeing the same problem now as before. Haven't tried the same fix yet, but wanted to get the ball rolling again. This seems like a pretty major issue for anyone upgrading from WordPress who uses anything more than the most trivial of formatting.