TinyMCE Editor Transition - Frequently Asked Questions (FAQ)
The KB Admin Tools is transitioning away from the Classic editor to the TinyMCE editor. This document outlines common questions about the transition and timeline.
- Why are you switching to TinyMCE?
- Where can I learn more about TinyMCE?
- When will the Classic editor be fully retired?
- Can I keep using the Classic editor as my default editor?
- Why don't I see the option to switch to the Classic editor?
- Why do certain documents only open in the Classic HTML editor, when most of my documents open in TinyMCE?
- Should I expect issues when editing older documents with TinyMCE?
- How can I provide feedback or report any issues related to TinyMCE or the Classic editor?
We know that the editing experience is a core aspect of working in the KB Admin Tools. In the time since the KB was created, some great third-party What-You-See-Is-What-You-Get (WYSIWYG) editors have become available. Several years ago, we made the decision to move to one of these tools so that we could focus on other parts of the KB experience.
After a thorough review of editors on the market, we selected TinyMCE to replace the KB's Classic editor. TinyMCE offers a modern user interface, up-to-date web standards, and a robust feature set.
We suggest using this document as a starting point: KB User's Guide - Introduction to the TinyMCE Editor
The Classic WYSIWYG editor will be retired on March 2, 2023.
Beginning on October 27, 2022, TinyMCE will become the universal default editor. You will no longer be able to use the Classic editor as your default, though you will be able to switch to the Classic editor if it is enabled for your space. When you switch to the Classic editor, you will see the Classic HTML editor first, and you will be able to toggle over to the Classic WYSIWYG editor.
KB spaces that were created after we began the transition to TinyMCE do not have the Classic editor enabled. Additionally, admins for some older KB spaces have opted to disable the Classic editor altogether.
Why do certain documents only open in the Classic HTML editor, when most of my documents open in TinyMCE?
There are two circumstances where both the TinyMCE editor and the Classic WYSIWYG may be disabled for certain documents:
In general, most documents won't have any problems being edited in TinyMCE, even if they've only ever been edited in the Classic Editor. There are a few exceptions that might mean you will need to give documents extra attention the first time you edit them in TinyMCE:
If the document contains accessibility issues, TinyMCE's Accessibility Checker will alert you to these when you try to activate the doc. Some of the most common accessibility issues include issues with headings, insufficient alternative text on images, and tables lacking captions and headers.
For more information, please watch the session at our 2022 KB User Group Meeting where we reviewed most of the common errors and how to fix them.
Lists are the other most frequent cause of issues opening documents in TinyMCE. This is because lists created in the Classic Editor often contain syntax errors (e.g. the elements are out of order, or the list contains elements that aren't allowed in HTML).
TinyMCE automatically fixes these syntax errors, and in doing so, it may change the formatting of your list. This is especially common in documents that used the KB's older plus/minus toggles (which we recommend converting into collapsible panels).
If you are having trouble fixing your document, please reach out to us at the email address below for assistance.
We would love to hear from you! Please use this form to send feedback or report any issues you may experience. If you need support, visit the KB User's Guide for help documentation or reach out to the KB Admin team at firstname.lastname@example.org.