Plugin Contributor
Ewout
(@pomegranate)
Hi! The PDF library (dompdf) was updated to the latest version, this probably be what’s causing this. I have done some tests and it appears the issue is fixed by enabling the option “Use alternative HTML5 parser to parse HTML” in the status tab.
This option has some history:
Dompdf has always parsed the HTML with the DOMDocument class by default. Some time ago, this started acting up when libxml got an update and PHP7 would throw errors. I made the backup HTML5 parser default and added an option in the Status tab to use DOMDocument instead, because the HTML5 parser is an old & unmaintained library that still gave issues for some people. The libxml issue was solved in dompdf 0.8.2 so I re-enabled it again and reversing the option (making the HTML5 parser optional)….
But now it looks like this is still suboptimal, so I may end up reverting to setting the HTML5 parser as default again.
Hi, just updated the plugin and ticked the “Use alternative HTML5 parser to parse HTML” in the status tab but still creating the PDF with wrong header margins 🙁
Back to v2.0.15 and it’s fine! Cheers, Iain
Plugin Contributor
Ewout
(@pomegranate)
Could you send a zip of your template (I saw from another thread you’ve customized a few things) and the resulting PDF to [email protected] so we can take a look at this?
Thanks!