Breadcrumbs

Scroll HTML Exporter 3.9.11

August 2020

We are happy to announce the release of Scroll HTML Exporter 3.9.11, which is a maintenance release. This release updates the bundled libraries used with the Scroll WebHelp theme template. Additionally, we have increased security for the app by checking requests for external content against the Confluence Whitelist - please see the additional information below as this change can impact on the generated export result. 

In this release, we have changed the way in which content/images that are hosted on a different server are handled. Now, images that are hosted on a different server will not be downloaded by default any more in order to improve app security. This means to allow content from an external host to be downloaded you will now have to enable this host through the Confluence whitelist settings. You can find the Confluence whitelist configuration screen in the global admin configuration under "Users & Security > Whitelist". To read more, please see the Confluence whitelist documentation for further information about how to configure this whitelist.


We are in the process of launching a Data Center approved version of Scroll HTML Exporter in Q3 and the app is going through the approval process to ensure it meets the Data Center approved standards set by Atlassian - for more details about these standards, see Atlassian's Data Center FAQs

Following approval, if you have a Confluence Data Center license, you will be required to purchase a Scroll HTML Exporter Data Center license upon your next renewal. Prior to launch, we will provide you with the steps necessary to renew or migrate your license. If you have any questions about this process, you can contact our team via support@k15t.com.

Resolved issues in this release

New Features and Improvements

Key Summary T Created Updated Status Resolution Data cannot be retrieved due to an unexpected error. View these issues in Jira

Bug fixes

Key Summary T Created Updated Status Resolution Data cannot be retrieved due to an unexpected error. View these issues in Jira