Thank you for the reply, and I totally agree. We've been running jserport on many Windows servers for several years without issue. Recently, we've begun moving a few development machines over to Linxux and we know just enough to be dangerous.
It does appear to be more of an issue with either node.js or PM2. I was just hoping someone here might have seen a similar error when following the install steps.
I will continue researching the issue looking more closely at PM2.
hi! jsreport by default has CORS enabled, I have done a test from a simple app at localhost:4000 and jsreport running at localhost:5488 and everything works as expected, both the preflight (the one with request method OPTIONS) and the normal request (the one with request method PATCH) pass
1.- Preflight request
2.- Save request
in your case it seems to be failing at the first request, which is the preflight request, since you have the api gateway in front of the jsreport server, it seems to me that this is a problem related to the api gateway, have you enabled CORS there? it seems to be easy to enable that in the console, maybe you are missing that step
I am afraid that chrome can set the margin only for the whole document.
Typically you solve your case by making an extra template with a different margin and you prepend it using pdf utils to the main template. Unfortunately, your "section 1" seems to be dynamic and spawns to multiple pages, so you can't use this approach. I don't know how to solve this at this moment.
I agree that it is a bit confusing but I believe this is handlebars specific knowledge and our docs are not the best place to explain it, there are lot of handlebars references in the docs and adding explanation of the syntax will be overwhelming
Disabled Categories are greyed out
This topic will be moved to the category
Looks like your connection to jsreport forum was lost, please wait while we try to reconnect.