After migrating a space to cloud via the CCMA, is the editor from the server used.
That’s currently the expected behaviour from what I understand. That editor is the classic editor, and was what Cloud used before the new Fabric editor was built. Since server pages are still in the classic format, that’s how they display until they’re converted to the new editor. Usually there’s a message or pop-up asking if you want to use the new editor and it will convert the format.
One advantage of this is that if you have nest body macros, you can edit the content to prepare for the new editor, as it currently doesn’t support them.
Thanks for the clarification!
Hi @jrichards can I confirm that this behavior is always true? Asking because one of our developers mentioned getting the new Fabric editors straight after migrating from Server.
I just did a quick, non-scientific test and found that simple pages that have no macros or “complex” content do open in the new Fabric editor, and that pages with macros or some sort of structure like a layout, do open with the older editor.
I don’t have an answer yet from the development team, but I’ll go with my non-scientific answer for now.