Visual Editor Disabled, Editing a Page With HTML Encoded Entities &lt;span&gt; changes them into <> changing the content

[foolswisdom]

Editing a Page With HTML Encoded Entities &lt;span&gt; changes them into <> changing the content

ENV: WP trunk (2.3+r6172)
User Profile > Uncheck (DISABLE) Use the visual editor when writing

Repro: Always
Steps:

1. Create a page with Page Content of
   

<span>

2. Publish the page
   
3. Edit the page again

ACTUALLY RESULT:
The Page Content is now
<span>

EXPECTED RESULT:
The Page Content should still be
<span>

[bglickstein]

As I described in my original report, issue #5084, this also happens in the other direction: non-encoded HTML entities become encoded.

[foolswisdom]

bglickstein, please try to isolate the "other direction" issue you are encountering and write a bug report with repro steps. Posts not pages? Can you only repro it with posts made from XML-RPC? What blog client are you using?

[Viper007Bond]

I'm unable to reproduce this using latest SVN. I did exactly as the original ticket described and I got the exact code I originally entered after editing the post.

[Viper007Bond]

Er, I misread. It works fine for posts, it is indeed broken for pages.

[johnbillion]

bglickstein, can you verify this bug still exists with all your plugins disabled?

[cosmix]

This seems to be a core bug. It is always reproducible without any active plugins on 2.3. I managed to get this working by adding the format_to_edit() and apply_filters() lines taken from the same function on 2.2.3 to the get_post_to_edit() found in wp-admin/includes/post.php at line 162 on WP2.3. Since I am not familiar with the design of WP and the changes that took place between 2.2.3 and 2.3 this might be a very wrong way of fixing this; this is why I am not attaching a patch here. In any case, I hope it helps someone to find a better solution.

[cosmix]

Note that the suggested 'fix' above breaks posts.

[raptorNL]

Problem seems to be fixed in the latest development revision (6226).

[ryan]

I think [6184] fixed this. Should be fixed in trunk and the 2.3 branch.

[ryan]

Resolving as fixed. If you can reproduce this using the latest from the 2.3 branch, please re-open.