Question
I am trying to use a macro in a versioned space, and it's not working properly. What's the reason, and how do I fix it?
Answer
In versioned spaces, every edited versioned page is an actual Confluence page. This is how Scroll Versions allows multiple different versions of the same page. Likewise, pages with Conditional Content for example display different content for different variants, despite all of it being in one page. Of course, Confluence 'sees' those pages as normal pages – and this often causes certain features, third-party apps or macros to behave in unexpected ways.
In Scroll Versions, we provide versions-compatible alternatives of the macros that are necessary for documentation authoring spaces (see the reference table below for details). Please keep in mind, that macros generally have more data to process in versioned spaces, which can lead to higher cache requirements or longer load times.
However, it's simply not possible for us to build alternative versions of every macro that behaves unexpectedly in versioned spaces – the support for certain features, apps and macros is considered a feature of Scroll Versions. If a certain macro or app doesn't work, this is not a bug.
Macro compatibility
Built-in macros
Third-party macros
| App/macro name | Compatibility | Notes |
|---|
| Gliffy |  |
|
| Balsamiq mockup | |
|
| Draw.io | |
|
| Multi Excerpt macro |  | See how Content Reuse is done in spaces with Scroll Versions |
