hi! sorry, i wanted to find the time to later check the example, but i completely forgot about it.. the problem is that you were not specifying the space for the header in TemplatePage2, i changed that template with a margin top of 40px and now it shows. you can see it here https://playground.jsreport.net/w/bjrmatos/u9kIVdEz

have you stopped and started again the jsreport process?

you should see logs like these in the end after you restart the jsreport process:

2018-10-04T15:02:51.220Z - info: jsreport server successfully started on http port: 5488
2018-10-04T15:02:51.220Z - info: fs store emits sockets to synchronize underlying changes with studio
2018-10-04T15:02:51.232Z - info: Verifying license key <here will be your key>
2018-10-04T15:02:52.069Z - info: License key verified as yearly subscription
2018-10-04T15:02:52.069Z - info: Storing license verification information to jsreport.license.json
2018-10-04T15:02:52.071Z - info: reporter initialized

NOTE: of course this part License key verified as yearly subscription will be different depending on the type of license you have

no, it should be in extra file called jsreport.config.json, which should be located at the root of your project, the file structure of your project would look like this:

and the content of the jsreport.config.json would be something like this:

{
  "httpPort": 5488,
  "store": {
    "provider": "fs"
  },
  "blobStorage": {
    "provider": "fs"
  },
  "licenseKey": "XXXXXXXXXXXXXXXXX",
  "logger": {
    "console": {
      "transport": "console",
      "level": "debug"
    },
    "file": {
      "transport": "file",
      "level": "info",
      "filename": "logs/reporter.log"
    },
    "error": {
      "transport": "file",
      "level": "error",
      "filename": "logs/error.log"
    }
  },
  "allowLocalFilesAccess": true,
  "templatingEngines": {
    "timeout": 10000,
    "strategy": "http-server"
  },
  "chrome": {
    "timeout": 40000
  },
  "extensions": {
    "authentication": {
      "cookieSession": {
        "secret": "<your strong secret here>"
      },
      "admin": {
        "username": "admin",
        "password": "password"
      },
      "enabled": false
    },
    "scripts": {
      "timeout": 40000,
      "strategy": "http-server"
    },
    "sample-template": {
      "createSamples": true
    }
  }
}

hi! i think this example satisfies what you are looking for

hi! here are the different ways of how to apply it: https://jsreport.net/learn/faq#how-to-apply-license-key, just FYI it is mentioned at the bottom of Buy page

I think we need to have greater control over headers and footers. The support for these so far is very limited and in reporting a major feature is header/footers.

agree with you, however what is possible today in most cases is enough. unfortunately we are limited to by what other technologies expose.

If you define a header, footer, height etc. within the chrome pdf properties in the JSReport editor.
Then on the page. If I decided to change the height for example, then If i could control the chrome pdf properties for that page, by accessing something like this.chromepdf.props.height = 0 or this.chromepdf.props.header = {#child template-header-warning......

as i've shown you can decide what should be the content of the header/footer per page already, so you can put there a dynamic value. however what is not possible is to change the page's margin or height per page, there is just one option for all pages, so we can say that all html to pdf converters expect that the content in header/footer is something static in the sense that it won't consume different space per page, so far there is no way we can change that because it is a limitation of the pdf conversion.

Is this something that can be done?

so in short, what you are describing it is not possible to do it in the way that you want. however i think you can workaround that problem by using pdf-utils append operation, so in the end you will be composing your pdf with pages of multiples templates, each of these templates can have different margins or height, so maybe you can try that and see if it is enough for your case.

i think what you are describing is possible. check this example to get an idea how to render dynamic content in header depending on the page number, etc.

https://playground.jsreport.net/w/anon/nXMgpqSu

the example will serve you as starting point for the complex report you want.

hi! nothing planned immediately, it is in backlog but for now we have other planned feature at the top of the list

oh so only with V2

you can also install pdf-utils in jsreport v1 using npm install jsreport-pdf-utils@0.x.x, but of course the 0.x.x versions of pdf-utils are considered outdated and maybe you will find some bugs or maybe not, you will need to test it and see if it works normally for what you will try to do in your template.

can you run v2 alongside 1.8.2 ?
of course on another port.

yes, you can do that, but if you want to share stored templates between the two versions the best will be to use an storage backed by a database.

@Carl-Blanchard hi! pdf-utils is an extension that it is pre-installed along with jsreport v2, so no need to install anything to get it. for usage check and some live examples the docs