Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Hi, I am trying to make a drupal book, print as a single pdf file in the same fashion that print friendly printer makes one print job.
When I make a PDF of the book, it only includes 2 pages of content, whereas the print link produces a 5 page print preview, all content is there, in PDF the rest is missing. When I switch to the other engine I get all the content without the images, in place of the images are little checkboxes with red Xs in them. this inconsistancy has to be a bug. the images are missing with dompdf and half the content is missing with tcpdf.
Comments
Comment #1
jcnventuraThe reason for those checkboxes in dompdf is that it can't find the images. I would have to take a look at the specific page to find the problem. Can you PM me a URL where I can test this?
João
Comment #2
spydmobile commentedThis is Drupal 6.9 on apache2 and PHP5 and Postgres/postgis 8.3 on Ubuntu server JeOS 8.10:
Print 6.x-1.1 with TCPDF 4.5.010 and dompdf 0.5.1
Comment #3
spydmobile commentedThis is an url to an image contained on the cover of the drupal book, it obviously has spaces in the filename, but it was also uploaded into the content by way of the build in image/file manager in the FCKeditor. That URL is accessible as a graphic by an unregisterd user, so permissions cannot be an issue.
Comment #4
jcnventuraIt's not me saying that it can't find it.. It's dompdf. The fact that TCPDF can find them means that the path is OK. The problem is that the two packages handle images in a completely different way. TCPDF tries to access them locally if it's running in the same server where the images are located. dompdf tries (I think..) to access them via the network, and depending on so many settings (apache, PHP), access to remote URLs from scripts may be denied.
As to the problem of TCPDF not printing everything.. Well, I do mention "Limited reproduction of the web page." in this module's home page. It's very good for text and images, but once you start adding tables, divs, spans and a lot of CSS, it simply can't handle it gracefully.
Try to execute dompdf directly in your server (http://www.digitaljunkies.ca/dompdf/usage.php#cli) and see if it provides some more info on the problem.. Use the HTML printer-friendly page as input, which reproduces this module's behavior more accurately.
João
Comment #5
jcnventuraNo further info in two weeks. Closing the issue.
João
Comment #6
jcnventura