[wp-hackers] wpautop is NOT the problem.

Chip Bennett chip at chipbennett.net
Fri Mar 18 15:19:40 UTC 2011

If you're switching between Visual and HTML editors, and you haven't
customized your TinyMCE configuration, you *WILL* run into problems.

I would suggest either not switching between editors, or else customizing
your TinyMCE configuration such that you avoid the changes that it makes
when switching from HTML to Visual.


On Fri, Mar 18, 2011 at 10:12 AM, Kevin Newman <CaptainN at unfocus.com> wrote:

> So after looking into this more carefully, to try and disable what I
> thought was the problem, I don't think the idea of wpautop is the problem,
> nor is the server side (php) implementation. If I just use the text editor,
> and save back to the server, things tend to work out.
> The problem seems to be the javascript implementation of wpautop that is
> triggered between TinyMCE and the HTML tab.
> The question then is, how to make this work more consistently like the PHP
> version.
> I think this could be handled with an Ajax call to the actual server side
> wpautop. But the JS version actually addresses another problem, which is
> that content coming out of TinyMCE needs to be formatted (it's also doing
> some other kind of filtering that I haven't looked closely enough at to
> understand yet) - that could be handled separately before or after the
> server side wpautop tag-back.
> Anyway, has anyone looked into this? I'd be a lot of the complaining about
> wpautop is actually complaints about the client side implementation of it,
> and not about wpautop in general.
> I'd be happy to attempt a solution, if there is any interest.
> Kevin N.
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers

More information about the wp-hackers mailing list