How do I include a specific version of a page?

[Vincent Spallek]

This question is in reference to Atlassian Documentation: Include Page Macro

Oftentimes, I need to include a specific (released) version of one page in another page. How can this be done?

[Radek Janata]

You can write your own user macro (we did it this way first but we had problems displaying embedded attachments/images from that page).

Or, you can use Adaptavist ScriptRunner for Confluence that has Include Version macro bundled. It displays embedded attachments/images correctly.

Check out their documentation:
https://scriptrunner.adaptavist.com/latest/confluence/macros/BundledMacros.html#_include_version_macro

[Timothy]

Don't think the Include Page Macro does that but you can place a link to the version of the page:

• http://wiki/pages/myviewpage.action?pageId=21364790&version=2

[Vincent Spallek]

We want to be able to print a collection of specific versions of pages as PDF. For that, I need to include them, not just link them, right?

[Nic Brough -Adaptavist-]

Correct, but the include macro will always take the current version of a page, that's what it's for.

[Vincent Spallek]

Is there another macro then that is for including a specific version of another page?

[Nic Brough -Adaptavist-]

No.

It's because a page in a wiki is in theory a live working document, so readers will generally always want to see the current version.

When doing documentation though, that can be wrong.  Atlassian themselves use "Scroll Viewport" on their own Confluence to support documentation properly.

[Nic Brough -Adaptavist-]

No, I'm afraid not.

Conflluence is a wiki, with an implicit assumption that the users will want to see the current version of a page.

This doesn't work too well for documentation though, and it's a bit of a weakness IMHO.  Even Atlassian admit it implicitly - their docs on the products are, of course, held in Confluence.  With Scroll Viewport in use to enable Conflluence to do the required "fetch version of pages related to specific versions of products".

[Vincent Spallek]

Scroll Viewport looks like an interesting solution that could solve our problems. Is something similar available also for Cloud hosting?

[Henk Aarts]

@Nic Brough -Adaptavist- You mention Scroll Viewport to manage page versions for publications. There is also a plug-in App Scroll Versions which indicates to do this as well. Although the license price is much higher then for Scroll Viewport. Do we need to use the Scroll Version in combination with Scroll Viewport to publish specific page versions as a package or is this functionality also include in Scroll Viewport? We are looking into a solution to publish a certain package version of a space.

[roman]

Hi @Henk Aarts, versions functionality is not included with Scroll Viewport, for this you would need Scroll Verisons.

Atlassian is using both Scroll Versions and Scroll Viewport to create, manage and publish their documentation. The version picker you see in Confluence documentation is achieved by publishing each version to a separate space with the help of Scroll Versions. The content on this published Confluence page is then added to a second "view" and presented with a custom Scroll Viewport template.

Scroll Versions is available for Confluence Server and can be tried out for free from the Marketplace.

Cheers,
Roman.