Placeholder Text Converted from Confluence is Rendered as-is

Thanks for the report. I attached the export to the ticket for posterity, and so we don't lose it when we come back to it.

Relevant extract: this appears to be the body content of a regular page:

<object class="BodyContent" package="com.atlassian.confluence.core">
<id name="id">75563010</id>
<property name="body"><![CDATA[<p local-id="2e3b32847040">First name: <ac:placeholder ac:local-id="fcca177b479e">Please enter your first name here</ac:placeholder></p><p local-id="9d1428cd150c">Last name: Iverson<br /><br />Note: Only the last name “Iverson” has been entered, but not the first name.</p>]]></property>
<property name="content" class="Page" package="com.atlassian.confluence.pages"><id name="id">76218369</id>
</property>
<property name="bodyType">2</property>
</object>

We can't really remove the placeholders like this because they are also used in templates, and we need the users to notice what to edit. I didn't know they could appear in regular pages as well, but I suspect some users might prefer to keep the placeholder after the migration in any case, so unconditionally removing the placeholder doesn't seem to be a good solution.

Leaving this ticket open for now as this is a valid concern and we pretty much need to find something satisfying. I guess that ideally, we'd have an equivalent feature in XWiki where these tests appear in a special way, and/or only during edition, and I agree that the situation is not ideal.

Solutions I can imagine would be to migrate the ac:placeholder tag to some macro that's only visible during edition, or having a parameter to drop the placeholder but then again, should we drop them only in regular pages? In template as well? I don't want to rush into adding yet another option without clear vision / good use cases in mind.

In the meantime, I would advise manual post migration fix. Hopefully this is manageable and not many pages are affected.