I assume that you would need to run the Classic Editor plugin to maintain the availability of the TinyMCE editor, and then also run the TinyMCE Advanced plugin to access those other features. You could should check this through a post in the TinyMCE Advanced support forum.
@pidengmor – Thank you for answering me.
Your answer makes perfect sense, but I just wanted to be sure. I think I also put this question on the TinyMCE Advanced forum. I will keep checking, but even if I could only use the Classic Editor plugin, I would still use it because my websites do not need to be changed for Gutenberg. The information on them is pretty static and they are not updated very often so I would prefer to maintain them as they are.
Thanks.
No problem. I’m also planning to retain the Classic Editor for the same reasons you give. Good luck!
I was advised by Jan Dembowski to install the Classic Editor on my website NOW, if I don’t want to deal with Gutenberg when it is released. However, at the Classic Editor Plugin page
https://wordpress.org/plugins/classic-editor/
it says not to install it on live websites, as it is Beta.
Has anyone used it successfully with a live website? Is it worth the risk?
Another option is to place the following* into the active theme’s functions.php file:
// Disable Gutenberg on update to WordPress 5.0+
add_filter('gutenberg_can_edit_post_type', '__return_false');
This will prevent Gutenberg from activating on update to WordPress 5.0, and the editor will fallback to the standard TincyMCE (aka Classic Editor) which will still be part of core for the time being. I have added this filter to 6 sites, and will now sleep a little easier at night.
Code from: https://digwp.com/2018/04/how-to-disable-gutenberg/
* Use FTP or a file manager to add this filter, and take a backup of the file before making any changes.
