[wp-hackers] wpautop is NOT the problem.

[Kevin Newman]

Hmm, I'll have to look into what they are doing behind the scenes.

Kevin N.


On 3/18/2011 11:18 AM, Helen Hou wrote:
> Are you talking about something like the way the TinyMCE Advanced plugin handles maintaining p and br in the editor?
>
> --
> Helen Hou-Sandi
> http://www.helenhousandi.com
>
> On Mar 18, 2011, at 11: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
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers