Page History

In the new editor you cannot do that and have to place ConfiForms IFTTT macros outside the ConfiForms Form Definition macro and you need to link the rules and the form via the "Form name" parameter

Place it outside and set the form name to point at your form. Also you can easily put this macro on a separate page if necessary. To decouple you form configuration and form presentation.

You still can have custom layouts for your form, but you need to be aware that you will not be able to put bodied macros inside this macro

Creating charts and graphs, filtering the tables with other plugins is impossible in Confluence cloud due to limitations of this platform and the new editor in particular

Yes, Atlassian has decided to remove lots of macros and we suggest to use "Code" macro as a workaround when "No Format" is mentioned in tutorials

https://confluence.atlassian.com/confcloud/we-re-cleaning-up-the-macro-browser-946028471.html

Unfortunately new editor for Confluence cloud sets lots of limitations and reduces lots of possibilities in layout customization. See the tickets referenced in other rows from this table and some more below

For ConfiForms IFTTT macros (for creating the pages in Confluence) this is somewhat dramatic - as ConfiForms IFTTT macro itself is a bodied macro and new editor lacks the support for nesting bodied macros you get a very very limited possibilities.

One workaround we advise to do is to use Confluence templates for the pages you create with ConfiForms and reference them instead of defining the page layouts within the ConfiForms IFTTT macro

This is blocked by issues (even marked as "fixed" issues are not really fixed )

This affects us in a way that when a static macro, such as DataView in ConfiForms, is rendered on a page we get 2 identical concurrent calls to our backend to render an output... instead of just one

Copy/paste from a legacy editor (or from server/dc editor) into a new Confluence (aka "fabric") editor