TinyMCE 6

Can you give me one (or more) specific examples of what you would like to see or be able to change with the TinyMCE Toolbar?

I ask because the default TinyMCE used in bbPress & Style Pack can pretty easily be extended with a few initialization arguments like:

args['tinymce'] = array('toolbar' => 'formatselect );

That example would initialize the TinyMCE editor with the font formatting selection drop-down as the ONLY button, and all other buttons removed.

On the opposite end of the spectrum is adding all kinds of buttons to the toolbar. Here’s a picture of the supercharged Topic/Reply TinyMCE toolbar on my personal site:

That’s just using some custom code hooks/filters against the existing TinyMCE editor to add all kinds of default buttons, and even integrating shortcodes from other plugins, smileys, a format highlighting code block, and all kinds of extra, unnecessary, useless junk that no one’s ever going to use. Why? Not really sure, but I did it anyway. ??

Honestly, most of what I did in the picture above, and probably anything that MOST PEOPLE would want can be accomplished with “the plugin formerly known as TinyMCE Advanced“, and it works with bbPress & Style Pack. Yeah, it hasn’t been updated in a while, but it still works fine (for now).

That’s kinda why I’m asking for examples of what you want. If there’s no real suitable options available and it serves a purpose that fits within the intent/scope of Style Pack, then I may be up for adding it.

@codejp3 It’s more about changing WP to use the newer TinyMCE core and not the old (now obsolete) version.

I already have a couple of plugins that give me extra functionality in the current toolbar. But WP should really be using the current version of the toolbar at the core level IMHO.

@codejp3 Also, I do you the plug-in you mentioned. ??

I am not missing functionality. I have what I need. Just a case of updating the core.

@codejp3 See:

https://core.trac.www.ads-software.com/ticket/47218

Gotcha. Loud and clear now.

What you want is wp-core modifications. Well beyond the scope of Style Pack. Looking at the core-track for WP, I see you’re already all over it:

https://core.trac.www.ads-software.com/ticket/47218

My input just from reading that thread and comparing changes from v4 to v5 or v6:

1.) I think the biggest issue is backward/forward compatibility. It’s as much TinyMCE’s fault as it is WP’s fault. WP went above and beyond to provide backward/forward compatibility between v3 and v4. It would be a HUGE undertaking to also extend that to make sure WP plugins written for v3 or v4 also work with v5 and v6. If TinyMCE provided internal backward compatibility, then it wouldn’t be an issue and WP would adopt newer TinyMCE versions quickly.

2.) WP seems to really be reaching for Gutenberg / block editor enhancements and wide-scale adoption, while gradually trying to phase out classic editors in the process, especially TinyMCE. With that in mind, it’s a really hard sell investing a ton of time into the compatibility issues mentioned in #1 above for something that’s a very low priority.

It’s beyond my skill-set and available time to take on a project of that size, but I’m certainly going to look at https://github.com/ClassicPress-research/ClassicPress-Editor and see if it’s realistic/practical/stable to allow the use of a newer version that overrides the default WP v4 (without breaking all current WP plugins written for v3 / v4).

Understood my friend.