SCROLL PDF Not working

[Anna Mas]

Hi, 

The Scroll PDF plug-in is not working properly, we get the following error message: 

[Fabio Racobaldo _Herzum_ · Accepted solution]

Hi @Anna Mas  and welcome,

please raise a support request to vendor portal https://k15t.jira.com/servicedesk/customer/portal/3

Fabio

[Anna Mas]

Thanks @Fabio Racobaldo _Herzum_ !

[Fabio Racobaldo _Herzum_]

you're welcome @Anna Mas 

[Thomas Rough _K15t_]

Hey @Anna Mas ,
Thanks for the post.

We, K15t (vendors of the Scroll PDF Exporter), are aware of this issue and have been in contact with Atlassian. They are still investigating this issue as it seems that a change has introduced an issue that affects any item in the page tools menu ••• that needs to open a UI dialog from there, such as the export dialogue for our app. This problem is also evident for other apps that also require a UI dialog to be opened from the page tools menu.

In the meantime, should you need to generate an export using our app there remains a few workarounds;

If you have global/space admin permissions (depending on the where the export template you want to use is located) you can go into the template editor for your desired template and select the Export option in the top right hand corner. This will allow you to then choose a page that you wish to export and you can generate the export directly from the template.

OR

Alternatively, if you don’t have admin permissions you can add the Scroll Export Button macro to your required page and then use the macro parameters to choose your export template and export scope. Selecting the button on the page will then allow the export to be generated. To access the Scroll Export Button in your instance you would need to install the free Scroll Exporter Extensions app.

OR

Lastly, you can also still use the REST API to successfully generate exports - you can learn more about this approach here.

All these workaround require no interaction with the affected page tools menu so will provide you with the option to export in the meantime whilst this issue remains open.

Regards,
Thomas

**************

Update: Atlassian has now logged an official incident for this issue and you can view it here - https://confluence.status.atlassian.com/incidents/3qzks006gprc

**************