The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

It looks like the p tag in line 38 isn't closed before you open the new one. Nested p tags are not valid. That would also explain your second error: end tag for "p" omitted, but OMITTAG NO was specified .

It may be a bug. Remember, Phoenix is in alpha now. I'm not even using it on my main blog. Let's keep testing. Turn on auto p and make a post with a couple of paragraphs, but no <!-- more --> tag. Then check validation and see if the p tags are getting closed. That may tell us if the more tag causes the problem, or if it's a general problem with the auto p plugin.

Alternatively, make sure you have 'enter enter' before AND After your !M link, though I've not tested that method. For me I have no text visible at the "read more" link after the visitor follows, so I don't want an empty paragraph there.

I use both auto-P and !M without causing validation errors, though I just now noticed I've got errors due to stuff other than this. For the record I'm using 1.7 Beta up-to-date as of a few days ago.

Just wanted to add my testimony in verifying this bug in 1.6... When using <!--more-->, <p> tags aren't handled properly; either they aren't opened, or aren't closed - and it seems to be that when they aren't opened, there happens to be the opening tag of a block level element immediately preceding (for instance, I'll have a <div> to contain the text, and Auto P doesn't bother to put an opening paragraph tag for that first set of text; but it does put the closing tag at the end of the paragraph).

So I've just now upgraded to version 1.7-beta on my local machine for testing purposes, and this bug still sort of exists. Here's what's causing the issue:

Currently, I use a specially classed <div> to style the paragraphs that precede the <!--more-->. If I write my post as follows with "auto-P" checked:

Code

<div class="special">

Here is the first paragraph of my text.

Here is the second paragraph of my text.

</div>

<!--more-->

Rest of my text...

Here's how it gets rendered:

Code

<div class="special">

Here is the first paragraph of my text.</p>

<p>Here is the second paragraph of my text.

</div>

<p><a id="more001" name="more001"></a><br />

Rest of my text...</p>

One lines-worth of space needs to be put between the div tags and the actual text therein in order for the paragraph tags to be opened and closed properly. So it needs to be changed as such:

Code

<div class="special">

Here is the first paragraph of my text.

Here is the second paragraph of my text.

</div>

<!--more-->

Rest of my text...

Once this is done, it renders just fine:

Code

<div class="special">

<p>Here is the first paragraph of my text.</p>

<p>Here is the second paragraph of my text.</p>

</div>

<p><a id="more001" name="more001"></a><br />

Rest of my text...</p>

But, if you don't use a div, or I'm presuming most any other kind of block element, to surround your text prior to <!--more--> (which I anticipate is the case for most people), then auto-P works properly.

So Maui, check to see if that's what's happening for you. I have yet to see if the same is true with version 1.6.

Maybe this isn't a bug much more than it is a knowing-usage issue, but it is a change from how things were before, and posts not done properly for 1.6/1.7 (as were all of my 0.9 posts) will have to be changed in order to validate.