Stop using heckyesmarkdown.com about wordpress-to-jekyll-exporter HOT 6 CLOSED

IIRC, the problem wasn't just warnings, it was not working in a handful of cases versus being slow in a handful of cases. Did you take a look at the Markdownify fork? If it's a drop in, think that's the way to go.

from wordpress-to-jekyll-exporter.

IIRC, the problem wasn't just warnings, it was not working in a handful of cases versus being slow in a handful of cases.

Like I said, Jekyll doesn't mind having HTML in .md files. Converting from HTML to Markdown is a "best-effort" sort of thing anyway.

Did you take a look at the Markdownify fork?

I don't know anything about that.

from wordpress-to-jekyll-exporter.

Oh, I saw your comment: a403c1e#commitcomment-3289100

from wordpress-to-jekyll-exporter.

Agreed. The problem, as far as I can tell, is that Markdownify is no longer supported and hasn't been updated in four years. Users were complaining of compatibility issues, this at least worked.

Ahh, it looks like there's a there's a fork now as well. Would be awesome to 🔥 that to the ground if either you or perhaps @ghelleks were interested in taking a pass?

Also background on the issues with legacy Markdownify.

When you said "parser errors", I was thinking of the HTML parser, not PHP errors. Those are bad, agreed.

from wordpress-to-jekyll-exporter.

Yeah, it would just 💥 on a bunch of user's installs. Will take a pass and send it your way for testing, if that works? (don't have a good WP install to test on)

from wordpress-to-jekyll-exporter.

Well, the install I have works fine with the old Markdownify, but ok, I'll keep it around for a while.

from wordpress-to-jekyll-exporter.