- πΊπΈUnited States kimble
Thank you so much for entity_print-dompdf-2969184-13.patch! You have saved me! I couldn't not run a test because my parameters were not available in the choices.
In my case, I applied the patch in this environment:
- entity_print:2.2
- Drupal 8.9 (On my way to ^9.4)
- PHP 7.4
- Maria DB 10.3 - last update
over 1 year ago 54 pass - π¦πΊAustralia marc.groth
Patch #13 no longer applies with the latest version of this module. Attached is a re-patch
- π¬π§United Kingdom ippy
Nice one, thank you. I just discovered the same.
Patch applied cleanly. Much appreciated. - Status changed to Needs work
over 1 year ago 4:34am 17 August 2023 - π¦πΊAustralia jannakha Brisbane!
Should 'enable_debug' be part of config/schema/entity_print.schema.yml
- π³π±Netherlands neograph734 Netherlands
Is this still an issue? I've attempted to fix a similar (the same?) issue in π DomPdf stops on encountering an unrecognised CSS property and should not Fixed , which is present in the latest release.
The approach there was to no longer treat the DomPDF messages as errors. By suppressing the PrintEngineException entirely as proposed in this patch, I suppose you will run into strange and hard to debug behavior when you cannot write the PDF (permission issues, out of disk space, etc.)
As explained in #3323264-5: DomPdf stops on encountering an unrecognised CSS property and should not β , we could still improve on a debugging system.