Skip to main content
Skip table of contents

Overriding the output of macros

The output of some Confluence macros are not optimal for display in a viewport. For example, if a theme uses Twitter Bootstrap ( as HTML5/CSS framework, the output of the warning macro is not compatible with the HTML required by Twitter Bootstrap.

Therefore Scroll Viewport provides the functionality to override the output of macros. To do so there are a couple alternatives with different complexities (sorted by complexity):

  1. Create a Velocity Macro Override to override the output of a arbitrary macro.
  2. Use a Macro Replacement provided by Scroll Viewport and style the output with a velocity template.
  3. Create your own macro to override an existing macro (planned).

Velocity macro override

The Velocity Macro Override is a simple way to define the output of a macro, based on the parameters of the macro.

To define and register a macro override simply create a velocity template in the theme using the naming scheme overrides/<macro-name>.vm. When Scroll Viewport renders a page that contains a macro with that macro-name it renders the template overrides/<macro-name>.vm and passes the macro parameters and the body (if existent) to the macro.

This approach only works for simple macros, because it makes only the macro parameters available to the rendering context, but does not "execute" the macro. This means, if a macro contains any kind of logic like retrieving data from the database or some calculation, this approach will not work.

Creating a simple macro override template

For example, to override the panel macro, create a file in the in overrides/panel.vm:

<div class="panel panel-default">
        <div class="panel-heading">
            <h3 class="panel-title">$params.title</h3>
    <div class="panel-body">

Available placeholders

In the macro override template the following placeholders are available:

  • $macroName – the name of the macro
  • $params – a map of parameters of the macro
  • $body – the body of the macro (null for macros with no body)
  • $stringUtils – org.apache.commons.lang.StringUtils
  • $stringEscapeUtils – org.apache.commons.lang.StringEscapeUtils

Since Viewport 2.1 also all placeholders as described in the Page Context are available as well.

Using a different template location

Its also possible to configure where with templates should be used for which template as follows:

$page.renderContent("include/include-content.vm", {
    "panel" : "overrides/special-panel.vm"


This was the standard approach in Scroll Viewport <2.0, however, we recommend using the naming convention /overrides/<macro-name>.vm as described above.

Macro replacements provided by Scroll Viewport

Scroll Viewport provides some macros that replace built-in macros. To do so, Scroll Viewport replaces the macros before rendering, and also allows to override the output with a velocity template.

The advantage of this approach is that users can just use the macros they are used to, and Scroll Viewport replaces them on the fly.

Styling the macro replacements

Just create a velocity template in overrides/<macro-name>.vm as described in Velocity Macro Overrides (above).

List of macro replacements

Currently the following Macro Overrides are available:

MacroMacro NameCompatibilityComments
Attachments MacroattachmentsPARTIALCurrently, the Attachments macro replacement is limited.
JavaScript errors detected

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

If this problem persists, please contact our support.