DIV and Paragraph beheaver in 2.1

I solved the whole p tag thing, but now I want the <!--more--> tags solved too. Does anybody know a solution for that problem?! I don’t want p tags around those.

I completely agree with buskerdog – those two gifs depict what I saw, and what I see now, perfectly.

IMHO this is a ridiculous “advance”. The wysiwyg editor is fine, and I use it a lot, but when I want to see the code then I WANT TO SEE THE CODE. I do not want to see part of it, leaving me to guess what the rest will be.

Or am I missing something here?

Thankfully I find some frustrated fellows like me around.
I posted this issue yesterday but with no response. I totally agree with owenkelly, while WYSIWYG is fine, the code should be INTACT whose meaning relies here. The idea behind doing some “code purification” is reasonable, but an option to disable it should also be provided always.
This issue should be “officially fixed” ASAP or WP will become more ridiculous while its reputation has fallen down a bit with the release of 2.1.

I have applied the disable wpauto plugin but this only works as a temp measure since if you try to edit the post again all of the DIV tags are replaced by P tags once again. This problem is really VERY annoying but I guess a temp measure to solve things is better than nothing. Here’s hoping they issue a fix ASAP.

I have found a kind soul who made my theme 2.1 compliant, and that actually fixed all the erratic <p> instead of <div>
It means that our themes have to be compliant and that 2.1 is NOT flexible. But my pb is now solved

#3669 Missing close <p> tag in wpautop should resolve this issue in 2.1.1. I think release candidate 2.1.1-RC1 was created before this fix was added, so it is NOT in the RC.

I upgraded to 2.1.1 and it’s still not working properly.

<div>
<a><img></a>
<a><img></a>
<a><img></a>
</div>

becomes

<div>
<a><img></a></p>
<p><a><img></a></p>
<p><a><img></a>
</div>

is it still broken in 2.1.1?

I think it might be a slightly different bug, but 2.1.1 is certainly producing bad html for me and preventing my site from validating properly.

Yes, it IS still broken in 2.1.1.

Try creating a div element with some text inside it in the code view. Then save it. Then open it again. It will be a paragraph with some text inside it.

It did that for me anyway!

It’s also troublesome for plugins like FLVPlayer that create their own divs and codes. The first time you save the entry it’s fine (because it creates the code after you save) but if you go back and edit anything about the post it will lose its code when you save it again. Annoying.

Replacing TinyMCE with an alternative WYSIWYG editor seems to do the trick. There are plugins for FCKEditor and Xinha available.

WP 2.1.1 has the same flaw with <!–nextpage–>, surrounding it in <p></p> elements so that effectively nextpage doesn’t work.

Bummer. Just tried in on fresh instal with default theme.

Glad other people have found similar problem.

Have posted twice before about this, guess not many people are using W.P 2.11 yet

WP 2.1.1 is broken

Admin Panel / Users / Your Profile / Use the Visual Editor when writing (untick) brings everything back to normal!

That doesn’t solve my problem. Although my problem might be a different one, actually. I just tested again. Without the visual editor, if my code is as I posted earlier:

<div>
<a>foo</a>
<a>foo</a>
</div>

it renders it as

<div>
<a>foo</a><br />
<a>foo</a>
</div>

which is fine. If the code is:

<div>
<a>foo</a>

<a>foo</a>
</div>

it puts <p> tags in to keep the white space, which is fine too, except that it doesn’t do them properly. It renders it as:

<div>
<a>foo</a></p>
<p><a>foo</a>
</div>

Note that there are two missing <p> tags: the first opening tag and the last closing tag. With three or more paragraphs, the middle ones are fine, and the first and last are still wrong.

Curiously, without the link tags, it’s still wrong, but slightly differently. It does the closing tag properly but not the opening one:

<div>
foo</p>
<p>foo</p>
</div>

I can live with all this because it is displayed properly in all the browsers I’ve tested it on, but it doesn’t validate. Obviously.

So it’s not the visual editor.