Topics created by evildmguy

try to think about the execution context of the functions you have.

your add function, which is defined as template helpers is executed in server side context, it does not have access to the DOM, that is why everything you define in template helpers can be called as handlebars helpers.

your sum function, which is defined as javascript function in page is executed in browser side context as a normal browser that loads a page would do. it can not access handlebars helpers, you can modify DOM here because you are in browser side context

remember that jsreport executes your template to get final html (generated by your template body, helpers calls and data), and then uses that html to evaluate it in a recipe which usually is a browser (phantom, chrome), so in that part everything you have as script tags inside your html is evaluated

one of the breaking changes of v2 is this, since your old script is using if (req.options.isChildRequest) you need to update that to if (req.context.isChildRequest). remember to review all breaking changes first when analyzing why something does not work in v2.

Thanks for the response! Really looking forward to the new release!

As far as getting it to work, I did a clone of jsreport-studio to a directory and then just ran 'npm install' and that reported errors. Maybe I messed up and that isn't a stand alone app that can run?

it should work, if you are still curious about jsreport-studio.. what version of npm do you have? we use npm5 all the time and the install works always, are you using npm 5 too? also maybe it would help more if you share the exact error message that you get after npm install.

I think I also have a corrupted report because recreating it with a new name and copy/paste the code and it works as I intend.

Thanks again for the help!

edg

Hey,

Sorry for all of this but thanks again for all of your help!

I was behind on node version (7.8) and pdf-utils (0.3.1). Once I updated them, I got the merge option -> render for every page to work.

Thanks!

edg

@Samerkassem I had the same problem. My solution was to add global helpers.js as asset, not as script and activate "shared helpers attached to each template".

Okay, I figured it was something stupid. Thanks!

As a note, I also had to stop and start the npm server that was running before it picked it up.

yes, that is expected, if you make some change in the config you should stop and start the server in order to recognize the changes.