WYSIWYG

Just disable (turn off) the wysiwyg and that's all. -- Unsigned before 06:44, 22 December 2007 (UTC)

This does not solve the problem in my case. Nor is it an answer to the subject of this page, which is an attempt to collect information on how and where wordpress /does/ process text, regardless of intent. Ideally possible: creating a complex page with classes on divs and other hidden elements inside the post, that a non-techy person can later edit using the wysiwyg editor. This is applied in a FAQ page on a current project. ∴ here…♠ 06:44, 22 December 2007 (UTC)

Not sure what happened to original history of this article

Not sure why the original article {How_Wordpress_Processes_Entry_Text} wasn't moved so as to save the history of this article, but User:Here wrote the original article on/about December 20, 2007.

MichaelH (talk) 00:29, 5 March 2008 (UTC)

wpautop() runs when content is displayed, not when it is saved

The documentation here seems to indicate that wpautop runs when a post is saved. However, wpautop is a filter on the the_content hook, line 108 of filter-templates.php (in 2.5.1):

add_filter('the_content', 'wpautop');

The documentation should be correct to indicate when the wpautop filter is applied.