Ok, so I fixed it. This is what I had to do:

• create a new jsreport server on my local
• export the data from the studio but leaving out the Group Excel template (ideally I would just fo a full import back into this file, but you can't perform a full import when you have this error)
• import that into my new local server
• create a new folder in the local
• change the short id to the missing short id from the error
• export from local
• import that .zip to the affected server.

When it loaded the Group Excel template was in the folder and can be accessed and deleted.

Hi Jan,

I attempted to delete the template using the API (using postman) and got this error:

{
"error": {
"code": 500,
"message": "Cannot read property 'folder' of null",
"stack": "TypeError: Cannot read property 'folder' of null\n at collectParentFolders (/app/node_modules/jsreport-authorization/lib/modificationListeners.js:32:17)\n at propagateVisibilityPermissions (/app/node_modules/jsreport-authorization/lib/modificationListeners.js:88:25)\n at <anonymous>",
"target": "/templates(2A9S6bGRs6GPRfIN)",
"details": []
},
"innererror": {}
}

Hi, I have a test server that is running on docker. I want to clear this server entirely and upload some updated reports.

There is a template called "Group Excel" which seems to be missing a parent folder.

How do I remove this template in the studio? I am unable to import new files or clear the server with this template here? If I made a new folder is there a way to access the configuration file in the studio to change it to match the missing folder?

@bjrmatos and @jan_blaha is there any update on this issue and version 2.6.0?

Hi @jan_blaha do you have any update on this issue and version 2.6.0?

We use docker as well.

We cannot move past version 2.4.0.

Our entire setup works using 2.4.0, but the minute that we update to 2.5.0 we get these errors.

I am not sure how we can make a replicable demo to show you. It can't be replicated in the playground.

Hi,

It is sometimes important for me to get logs when using chrome-pdf, the only way that I can access the logs is through the studio startup page, however it is often cut off. How do I get the complete logs. See log is cut off at +938

I have tried to wait for the printing trigger.

Thank you.

Hi, just refining the question here.

If I run the template in version 2.5.0 i get this error:

Protocol error (Runtime.callFunctionOn): Target closed.
Error: Protocol error (Runtime.callFunctionOn): Target closed. at Promise (/app/node_modules/puppeteer/lib/Connection.js:183:56) at new Promise () at CDPSession.send (/app/node_modules/puppeteer/lib/Connection.js:182:12) at JSHandle.jsonValue (/app/node_modules/puppeteer/lib/JSHandle.js:87:43) at JSHandle. (/app/node_modules/puppeteer/lib/helper.js:111:23) at ExecutionContext.evaluate (/app/node_modules/puppeteer/lib/ExecutionContext.js:49:33) at at process._tickDomainCallback (internal/process/next_tick.js:229:7) -- ASYNC -- at ExecutionContext. (/app/node_modules/puppeteer/lib/helper.js:110:27) at DOMWorld.evaluate (/app/node_modules/puppeteer/lib/DOMWorld.js:112:20) at at process._tickDomainCallback (internal/process/next_tick.js:229:7) -- ASYNC -- at Frame. (/app/node_modules/puppeteer/lib/helper.js:110:27) at Page.evaluate (/app/node_modules/puppeteer/lib/Page.js:782:43) at Page. (/app/node_modules/puppeteer/lib/helper.js:111:23) at runWithTimeout (/app/node_modules/chrome-page-eval/lib/eval.js:179:39) at at process._tickDomainCallback (internal/process/next_tick.js:229:7)

+0 Starting rendering request 823 (user: reports)
+3 Rendering template { name: excelTables, recipe: html-to-xlsx, engine: handlebars, preview: true }
+7 Adding sample data BkxQsl9E1B
+12 Resources not defined for this template.
+15 Base url not specified, skipping its injection.
+15 Rendering engine handlebars
+35 Taking compiled template from engine cache
+50 Executing recipe html-to-xlsx

If I roll the server back to version 2.3.0 and run the exact same template then it works.

Currently I am not able to use version 2.5.0 because of these errors.

Hi, I should probably emphasise that this error only arises after updating to 2.5.0

If I run the exact same template and the exact same data in an earlier version I do not get this error.