WordPress Adding Spurious </p>

[singpolyma]

If you look at this page: ​https://singpolyma.net/2011/06/dystoparx-part-12/ WordPress seems to be adding extra </p> tags before the </div>s This causes major well-formedness problems on the page.

[nacin]

Please post the HTML you have in your post content. We need before and after.

[ipublicis]

I checked the code on some of the other more recent posts and it doesn't show anymore. This has more than one year. Shouldn't it be closed?

[SergeyBiryukov]

There are still excess </p> tags in the linked post, but I couldn't reproduce the issue by copying the content from the HTML source (also tried switching to visual editor and back to HTML) neither in 3.4 nor in current trunk.

Free free to reopen with steps to reproduce if there's still a problem.

[singpolyma]

​http://pastie.org/4466275

That's the input as showing on my WP dashboard. I tried saving again and with X-Valid turned off as well, just in case that was transforming it (but it's not, still shows as fine in the dashboard), but it's still got the extra </p> in the page.

[SergeyBiryukov]

Confirmed when pasting the linked input into HTML (Text in 3.5) editor, saving and viewing the post.

After switching to visual editor and back, the extra </p> is gone.

[singpolyma]

I enabled the visual editor, switched to it and then switched back, and it broke some of my other markup, but after fixing that it does seem to be a workaround for the issue.

Still seems like a bug, though.

[azaozz]

Got it down to this:

• Extra closing P

  <div><p>123</p> </div> 
  

• Works as expected

  <div><p>123</p></div> 
  

Generally autop should ignore the whole content as there are no line breaks in there. What happens in this case: autop inserts a line break after the </p> and then threats the white space as another row.

A temporary workaround would be to remove all spaces between block tags.

[SergeyBiryukov]

Related: #20444

[mbijon]

Related: #21689
(via @Japh)

[jond]

Autop.php unit test coverage for #18136

[jond]

Added test coverage based on @azaozz findings.

[jond]

Fixed expected results

[MikeHansenMe]

Looks like this still needs a patch but already has unit tests.

[jond]

@MikeHansenMe See the patch applied to #27350. The fix for #27350 also fixes #18136 and passes unit tests.

[SergeyBiryukov]

Related: #43387

[dionysous]

Because we are encountering the same problem, I added a comment in #43387, when this is happening on our websites. Since this produces invalid HTML in the frontend, we get many reports about this.

[pento]

Closing this as a duplicate of #27350, which has the same root cause.