Topics created by B_Brights

Here is the migration guide for the technical part.
https://jsreport.net/learn/v3-migration-guide

In case you purchased jsreport subscription which is still active, you can simply update your app. In case you purchased a perpetual license, please contact us at sales@jsreport.net.

You can just copy-paste the application folder as long as you copy between the same architectures.
For example between windows->windows, ubuntu->ubuntu.
Then run node server.js.

jsreport uses script-manager to evaluate user javascript code.
This happens every time jsreport is evaluating templating engine of your template or your custom script.

Not sure what could be a problem here. You would need to elaborate more on the details.

However, maybe this is an option for you... Later today we should release stable jsreport v3. It has different architecture and doesn't use a script manager. You could try to deploy and see if the problem is solved. Or we would analyze together what's wrong.

Hi, it depends. You can run the report with debug button in the toolbar and see what is the bottleneck.
In some cases, it is a custom script that you could be able to optimize.
But in some cases, the bottleneck is the "chrome-pdf" printing which is hard to optimize and there is no configuration in jsreport that could help. The only approach is to try to remove some CSS styles and step by step find out what is slowing down the most.

You can share your debug output here and we can see what you can do.

I sincerely appreciate for your help

This means the first page should have a bigger header and the rest of the pages should have a smaller header?
And the content extends to the following pages without any control and intentional page breaks?

You can't get the page number in the main, because the information about pdf isn't ready before the main pdf rendering finished. What you can do is render the main, parse it, and render it again, but now with the information you collected during the parse.

See this part of the documentation
https://jsreport.net/learn/pdf-utils#usage-in-script

hmm your CentOS machine is probably missing the fonts needed to support the Thai characters, you need to identify which fonts you need to install.

i tried to search for some history about your problem and the closest is this , which in the end the user says that it got solved by installing different types of fonts, unfortunately, it did not say the font names. i found also this, which it claims that it gets the Thai characters supported just fine, you probably can check that to get the necessary font-names you need to install on CentOS