Skip to main content
Skip table of contents

Build Scroll Sites Optimized Macros

Whether a third-party macro is supported by Scroll Sites and whether it will display correctly in a site, depends on various factors, including whether your macro is/will be a static or dynamic content macro.

This page will just give some general pointers to:

  • help you identify if your existing macros will work in Scroll Sites

  • understand why your macros don’t work in Scroll Sites

  • how you can develop macros that will work in Scroll Sites

Please note, the information on this page is about Connect macros. How to build Scroll Sites optimized macros with Forge is not documented yet.

Static content macro

Static content macros may be supported out of the box. We recommend to test this out by putting together a page with the macro and publishing it to a Scroll site.

Please reach out to us at help@k15t.com if the output shows in Scroll Sites but not as expected.

Dynamic content macros

For your macro to show up in Scroll Sites it needs to support the export_view format. You can implement this by adding the default RenderMode to your macro.

If you want to verify the export_view format output of your macro on a specific Confluence page, you can use the body.export_view expansion.

Troubleshooting

User impersonation: no valid active user exists

If your macro backend uses user impersonation to access the Confluence REST API, there is a Confluence bug that prevents impersonating other app users. Since Scroll Sites uses its app user to access the export view, your requests against the Confluence REST API will fail with the following error message: Add-on '...' disallowed to impersonate the user because 'no valid active user exists'.

As a workaround, in cases where the Scroll Sites app user (account ID: 5de7d8e3ba60e10cfd68077e) is accessing your macro, use your own app user (using JWT authentication) to make requests against the Confluence REST API. As an additional security measure you may use the content permission check API to manually verify that the Scroll Sites app user has read access on any content object that you load from Confluence.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.