WordPress Import creates a new input format which is assigned to all imported nodes. This input format does not have 'Filtered HTML' enabled by default.
First, this means that any nodes imported with poorly-formed HTML will display as-is and invalidate the HTML and cause possible display problems.
Second, even if all the imported node HTML is valid, a teaser view can still split a tag in half, again invalidating the HTML and breaking the page. I observed an unclosed strong tag in a node teaser, thus applying strong to the rest of the HTML following.
The WordPress Import input format should have the Filtered HTML input format enabled by default.
Comments
Comment #1
mgladding CreditAttribution: mgladding commentedI would really like to see the ability to choose an input format for the import: wordpress, filtered HTML or full HTML.
Comment #2
kmontyIn 2.x, I noticed it created a wordpress format, which basically means you have a legacy format that you can customize. Is that really a bug?
Comment #3
yrocq CreditAttribution: yrocq commentedWe don't use html filter because it strips a lot of tags by default and it could cause some content to disappear in drupal (like object tags, etc). The "HTML corrector" filter may be a better option to fix html in the teaser.
Comment #4
kmontyI'm using the html corrector in my wordpress legacy input format. It seems like a good addition to me.