sapui5tutors SAPUI5 • Fiori • SAP BTP Step-by-step tutorials Real project examples Interview Q&A
Practical SAPUI5 • Fiori • SAP BTP tutorials and interview prep

TinyMCE 5 to 7 Migration in SAPUI5 RichTextEditor: What Breaks and How to Fix It

Your RichTextEditor just changed engines

Heads up — this one bites quietly.

TinyMCE 5 is removed from SAPUI5 entirely (all LTS versions: 1.96, 1.108, 1.120, 1.136, 1.142). TinyMCE 6 is deprecated. sap.ui.richtexteditor.RichTextEditor now runs on TinyMCE 7.

Stock editor with default config? You'll likely notice nothing. Custom plugins, toolbars, or skins? Keep reading — that's where things break.


What actually breaks

  • Custom plugins written against TinyMCE 5/6 APIs — removed APIs fail silently or throw. The big one.
  • Toolbar/menu configs referencing moved or renamed buttons.
  • Custom skins or content CSS targeting old DOM structures and class names.
  • Deprecated options carried in your config for years — TinyMCE 7 drops several.

TinyMCE's own "Migrating from TinyMCE 6 to TinyMCE 7" guide is the official reference. The SAPUI5-specific part is knowing where your customizations live. Here's the checklist:


Migration checklist

1. Find every RichTextEditor

Search for sap.ui.richtexteditor.RichTextEditor usages — and more importantly, custom configuration objects. Stock usage = low risk. Custom plugins, toolbar, or setup callbacks = needs review.

2. Inventory your custom plugins

Check each against the TinyMCE 7 API: renamed editor APIs, changed event names, removed legacy shims. The most common breakage: plugins calling APIs deprecated in 6 and removed in 7.

3. Update toolbar and menu configs

Walk your toolbar strings item by item. Dead buttons simply don't render — a silently degraded editor, the worst kind of bug.

4. Test the editor, don't just load it

Loading without errors ≠ working. Type, format, insert links and images, hit every custom plugin button, save and reload. The bugs hide in the interactions.

5. Check your UI5 version alignment

Confirm your UI5 version carries the TinyMCE 7 editor — and that no custom resource path pins an older one. Mixed versions are the classic "works on my machine."


My honest take

Most apps: a half-day task. Inventory, test, fix one or two toolbar items, done.

Deep editor customizations built over years: budget real time and test like you mean it. Either way, don't defer — TinyMCE 5 is gone, not deprecated, and 6 is on borrowed time.

Hit a specific migration error? Paste it in the comments and I'll take a look.