[wp-hackers] wpautop is NOT the problem.

Helen Hou-Sandi helen.y.hou at gmail.com
Fri Mar 18 18:17:30 UTC 2011

I found these pretty comprehensive, both addressing using a custom button
for a shortcode, but should be easy enough to use it for <code> instead:
http://brettterpstra.com/adding-a-tinymce-button/ and

I haven't made my own buttons, but I have added some of the bundled TinyMCE
ones and pre-built plugins. I found dissecting the source of the TinyMCE
Advanced plugin (another mention, jeez) to be the most helpful, especially
with keeping things in a certain order instead of just tacking stuff on at
the end of a toolbar.

The WordPress source itself is also a great reference for all the init
options :)

Helen Hou-Sandi

On Fri, Mar 18, 2011 at 12:31 PM, Dougal Campbell <dougal at gunters.org>wrote:

> On Mar 18 2011 11:19 AM, Chip Bennett wrote:
>> 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.
> Do you have any links to resources that explain how to customize the
> TinyMCE instance in WP? I've been wanting to add a button for a <code> tag
> (there's one in the quicktags, but not in TinyMCE, and I use it pretty
> often), but the process of customizing TinyMCE buttons has been pretty
> opaque to me.
> --
> Dougal Campbell <dougal at gunters.org>
> http://dougal.gunters.org/
> http://twitter.com/dougal
> http://twitual.com/
> _______________________________________________
> 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