Clickable image in subtemplate (merged) doesn't work

Marián Horňák

I am trying to use this clickable image in subtemplate which is used as footer with pdf-utils merge operation.

<a href="https://facebook.com">
    <img src="{#asset fb.png @encoding=dataURI}" width="20">
</a>

Image is rendered but there is no link (tested in playground jsreport version 3.5.0)
here is playground link created as anon, I hope it will be there some time (fb login doesnt work btw...)
https://playground.jsreport.net/w/anon/c5E63npa

Is there any workaround to achieve this, or am I missing something?

In version 3.3.0 it throws exception:
Error while executing pdf-utils operations. Cannot read properties of undefined (reading 'compressed')

Error while executing pdf-utils operations. Cannot read properties of undefined (reading 'compressed')
Error: Error while executing pdf-utils operations. Cannot read properties of undefined (reading 'compressed')
    at module.exports (/opt/jsreport/node_modules/@jsreport/jsreport-core/lib/shared/createError.js:10:13)
    at WorkerReporter.createError (/opt/jsreport/node_modules/@jsreport/jsreport-core/lib/shared/reporter.js:47:12)
    at AsyncFunction.<anonymous> (/opt/jsreport/node_modules/@jsreport/jsreport-pdf-utils/lib/worker.js:191:22)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async ListenerCollection.fire (/opt/jsreport/node_modules/@jsreport/jsreport-core/lib/shared/listenerCollection.js:157:21)
    at async afterRender (/opt/jsreport/node_modules/@jsreport/jsreport-core/lib/worker/render/render.js:104:5)
    at async WorkerReporter._render (/opt/jsreport/node_modules/@jsreport/jsreport-core/lib/worker/render/render.js:152:7)
    at async /opt/jsreport/node_modules/@jsreport/jsreport-core/lib/worker/reporter.js:177:19
    at async Domain.<anonymous> (/opt/jsreport/node_modules/@jsreport/advanced-workers/lib/workerHandler.js:141:19)
caused by: TypeError: Cannot read properties of undefined (reading 'compressed')
    at parseObject (/opt/jsreport/node_modules/@jsreport/pdfjs/lib/object/reference.js:81:15)
    at PDFReference.get [as object] (/opt/jsreport/node_modules/@jsreport/pdfjs/lib/object/reference.js:15:17)
    at Function.addObjectsRecursive (/opt/jsreport/node_modules/@jsreport/pdfjs/lib/parser/parser.js:61:35)
    at /opt/jsreport/node_modules/@jsreport/pdfjs/lib/parser/parser.js:82:18
    at Array.forEach (<anonymous>)
    at Function.addObjectsRecursive (/opt/jsreport/node_modules/@jsreport/pdfjs/lib/parser/parser.js:81:15)
    at Function.addObjectsRecursive (/opt/jsreport/node_modules/@jsreport/pdfjs/lib/parser/parser.js:77:18)
    at Function.addObjectsRecursive (/opt/jsreport/node_modules/@jsreport/pdfjs/lib/parser/parser.js:68:16)
    at parsePages (/opt/jsreport/node_modules/@jsreport/pdfjs/lib/external.js:38:18)
    at new ExternalDocument (/opt/jsreport/node_modules/@jsreport/pdfjs/lib/external.js:47:5)

jan_blaha

Thank you for the complete problem description.
I've checked and we should have this fixed in the next release.
It should be released in the next days.

Felix Frühstück

@jan_blaha , do you already know a rough timing for the fix?
Thank you in advance!

jan_blaha

It's published now
https://jsreport.net/blog/release-380