It is weird, but if I use pdf utils with phantom, $pdf.pages is always without items and group, but if I use with chrome-pdf - everything is okay.
Thanks.
deepdeer7
@deepdeer7
Posts made by deepdeer7
-
RE: pdfAddPageItem and pdfCreatePagesGroup work fine using chrome-pdf and don't work using phantom-pdf
-
RE: pdfAddPageItem and pdfCreatePagesGroup work fine using chrome-pdf and don't work using phantom-pdf
I mean, is there anything like this for phantom-pdf ?
$pdf: {
// array representing pdf before the current operation started
pages: [{
// explained bellow
items: [{}],
group: {}
}] -
RE: pdfAddPageItem and pdfCreatePagesGroup work fine using chrome-pdf and don't work using phantom-pdf
Maybe you know, is it possible in phantom-pdf making such a thing like a variable will be accessible in specific page? I mean, that after
<div style="page-break-before: always";></div>
I need that in units my custom header understands that it goes to new page.
-
RE: pdfAddPageItem and pdfCreatePagesGroup work fine using chrome-pdf and don't work using phantom-pdf
Thank you for replying. Yes, I mean native header. So now is it impossible using pdfAddPageItem and pdfCreatePagesGroup in units in phantom-pdf ?
-
pdfAddPageItem and pdfCreatePagesGroup work fine using chrome-pdf and don't work using phantom-pdf
This code works in units using chrome-pdf, but doesn't work using phantom-pdf. Please, help. And if pdfAddPageItem and pdfCreatePagesGroup can be used in header/footer in phantom-pdf? please say how (thought I doubt about this possibillity)
in units:
{{{pdfAddPageItem age}}}
{{#with (lookup $pdf.pages $pdf.pageIndex)}}
This page is in the group with value {{{group}}}
{{/with}}in main template:
{{{pdfCreatePagesGroup name="Jan" age=33}}}
{{{pdfAddPageItem name="Jan" age=33}}}