Could this be a login issue?

hmm i don't think that is be the problem. it will be weird that the user credentials are the problem.

different login for API vs. online editting?

i see that you have a "sails_user" so i guess this is the user that you use for your http API calls, so the other user gordon@149photos.com is the one that you use for the web login and for template editing, right? maybe something to try is that you try to login with the sails_user and try to save a template and see if you have the same error.

i would like to see the chrome console that you have when trying to save the template, maybe there are some errors there, also it will be great if you can inspect in chrome the request that was done to save the template, basically i would like to see the details of the request that is showing the prompt (headers, body, response). maybe you can send some screenshoots like the following, or event better copy the information from there and paste it here

PD: to upload images here, first click the blue button "Reply" and the drag and drop images in the new textbox that appears

we just need to finish the 2.6.0 release and then we start to plan the next tasks.

Are you depending on others to fix something?

we can fix it by ourselves (in this case we don't depend of external lib/mantainers), i think @jan_blaha will take care of this, there are some improvements for pdf-utils that need to be done and this issue will be included there too.

Can i help?

yes, basically you will need to debug why this line throws error when parsing the external PDF, but it can be tricky because it may require some knowledge of the PDF spec.

i understand this is a problem that stops you.. the pdf parsing is a bit tricky so from time to time there will be always a case in which the parsing fails and we need to do fix

@AB-D so far we have updated the chrome version in docker from Chrome 73 to Chrome 76, so that should solve the problem in the incoming jsreport 2.6.0, but we are going to do the release in one or two days.

@Css-IanM thanks for creating an issue for this, let's move the conversation to the github issue, we will reply to the issue when we have analyzed the use case a bit more with the team

hi! this is something hard to know, because it is really specific to Highchart's support for printing. maybe it needs some tweaks but i don't have the enough experience to tell you what can fix it or if you will have other problems with the charts in other scenarios. i only have some experience with Chartjs, which is the library i've used to create some of the showcase demos here. you can check this showcase how i was able to create a lot of charts and using margins in the page, maybe there is some style that can help you to fix your issue with Highcharts, i remember having some similar problem also with Chartjs but i was able to solve those by using some options { responsive: true, maintainAspectRatio: false, } when creating the charts., maybe there are similar options in Highcharts that you can try

hi! hmm yes, i tried this and it seems that it is a bug with some internal library that we use, for some reason the pdf parsing from buffer fails with these PDF files. i've created an issue to solve this, you can subscribe there for progress. thanks for making us aware of this problem.

hi, sorry for the wait, i just tested the authentication with your tenant and i can't replicate the issue, i don't see the authentication prompt. maybe the issue is gone by refreshing the browser cache, and cookies. i'm almost sure that it will be the case, but let me know how it goes.

ah ok, so this is jsreportonline, right? hmm if it does not get fixed by refreshing browser cache, share with me your tenant name (https://[tenant-name].jsreportonline.net/) and i will try to check what is happening with your account.

hi! when it started to happen? did you do something that maybe trigger it? (like updating jsreport or restarting it, or maybe changing the configuration) i just remember one similar case when this was happening, but it was resolved but refreshing browser cache, deleting cookies and restarting jsreport.

haha yes, sometimes it is easy to miss that, great that it is working now 👏👏👏