The Tiptap UI currently does not support using custom styles for your rich text.
I don’t imagine we will just be able to change the datatype of a rich-text field from Umb.PropertyEditorUi.TinyMCE to tiptap and my richtext html value will still just be there, right?
Is that what we are supposed to do while we are still on v15 before we upgrade to v16? What happens if we don’t switch to tiptap and that editorUI is just gone in v16? Will we still be able to use TinyMCE somehow as a plugin?
The out of the box tiptap editor in Umbraco strips out style=“” and class=“” in my html. It sounds like what I’m supposed to to is write my own extension in order to preserve those?
I think out of the box v16 needs to provide the ability for a more full html schema
Umbraco is moving from Tiny MCE to TipTap because of changes in with the TinyMCE license. The last version of Tiny MCE that had a compatible license with the CMS is now no longer supported. Later versions of TinyMCE are no longer license compatible with Umbraco and so cannot be included in the core product (Umbraco 15 Release Candidate).
However there is nothing preventing a community member creating a TinyMCE package for Umbraco that utilises the latest version of Tiny MCE and it is highly likely that someone will do so before we reach the next LTS release
I think the idea is that TipTap should have feature parity with TinyMCE before Umbraco 16. It’s almost there, but not 100%. Also the data should be interchangeable between TipTap and TinyMCE. I guess it’s the little things how it handles certain scenario’s where the changes are between the two.
Yes, you can already now migrate your data types to Tiptap in Umbraco 15. Come Umbraco 16, we will migrate any existing data types in the core and try to map over the toolbar, blocks, and other settings for you.
We expect a package from Tiny & Partners soon reintroducing TinyMCE to Umbraco and upgrading it to the latest version.
This is good to know, and I think we have addressed this in 15.3 for most ordinary tags so they will be preserved. Tiptap is quite strict on what is accepted. We’d like to know if you encounter anything else in the discussion on GitHub.