Publish to a Remote Confluence System
The app Scroll Remote Publishing Endpoint is only available for Confluence Server which will be unsupported from onwards, and we do not have plans to bring back this functionality to Cloud.
Please reach out to us via help@k15t.com if you have any questions.
If you have an internal Confluence in a secured environment and a separate public Confluence for your readers, you can publish to the public system using Scroll Versions on your secured authoring system and the Scroll Remote Publishing Endpoint installed on the public Confluence instance.
To use Scroll Remote Publishing Endpoint you must also have a license for Scroll Versions.
Use Scroll Remote Publishing Endpoint with Scroll Versions
To publish remotely you need to install Scroll Versions on your Confluence publishing system, and Scroll Remote Publishing Endpoint on the Confluence target system. Confluence Application Links are used for communication between the two systems. You can publish to a completely new space in the remote Confluence, or update existing spaces. Whether you publish within the same Confluence system or to a remote Confluence system makes no difference for your readers: they won't see any Scroll Versions functionality in the target space and the space looks like a standard Confluence space.
Prerequisites
To publish versions to a remote Confluence system, you have to meet multiple prerequisites:
Scroll Remote Publishing Endpoint must be installed on the target instance
Scroll Versions must be installed on the publishing system
The release versions of Scroll Versions and Scroll Remote Publishing Endpoint have to match
The publishing user must exist on both systems, with matching usernames. On the target instance, the user must have create space and create page permissions
You must establish an application link to the target system using the OAuth (Impersonation) authorization protocol
You should only use OAuth (Impersonation) authentication to establish the application link – this method does not work with other authentication protocols.
Publish to a Remote System
Once the application link is set up correctly, you can select the remote system in the publishing options when publishing to a new or existing space.
To publish to a remote system follow the steps below:
Click on the Scroll Versions Menu (≡) > Publish Version.
Choose To a new space or To an existing space.
Select the name of your remote Confluence system in the System dropdown.
Define the space key of the new or existing space.
Click Next and configure the remaining publishing settings before publishing.
Publish with permissions and restrictions
Scroll Remote Publishing Endpoint can't recreate user restrictions and permissions from the versioned authoring space. In other words, restrictions and permissions from your versioned space will not get published to the remote Confluence system. Therefore, after publishing you should apply potentially important page restrictions and space permissions again to your remote space.
If you have applied permissions and restrictions to your remote space then these will not get overwritten the next time you publish.
Elements displayed in an unexpected way on the published page
After publishing, certain elements may not be displayed as expected in the remote instance. The behavior may differ depending on whether Scroll Versions is installed in the remote instance:
Element | Behavior with Scroll Versions installed | Behavior without Scroll Versions |
|---|---|---|
Page titles | The Scroll Page Title of the source pages is published as the page title, and the permalink will be visible in the URL. Prerequisite: Scroll Translations is not enabled in a master space. | If Scroll Versions duplicate page title feature is activated in the source space, the permalink of pages is published rather than their title. We've documented a workaround here: VSN-3324 - currently there's not much we can do to improve this situation beside that. |
Page keys | Page keys are displayed in the remote space | Page keys are not available in the target space |
Scroll Pagetree macro | Displayed as in the authoring space | An "Unknown macro" message is displayed instead of the macro. The scroll page tree macro should be converted to a standard Confluence page tree macro when published, we are tracking this behavior at: VSN-3483 |
Scroll Metadata macro | The metadata macro is published to the page with the same settings, but because the published page will have different metadata to the original (there will be no versions, no workflows, and no attributes on the published page), the macro will not display the same output as in the source page | An "Unknown macro" message is displayed instead of the macro |
Gliffy and Draw.io diagrams | Displayed as in the authoring space | An "Unknown macro" message is displayed instead of the macro. We are tracking this behavior at: VSN-2013 |
Excerpt Include+ macro | Displayed as in the authoring space | An "Unknown macro" message is displayed instead of the macro. We are tracking this behavior at: VSN-3493 |
Include+ macro | Is converted to Confluence's standard Include macro, and displays content as expected | |