Closed (fixed)
Project:
Entity Print
Version:
8.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
11 Feb 2021 at 23:45 UTC
Updated:
20 Dec 2023 at 14:40 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
julien.sibiHi,
here is a small patch to remove dompdf requirement from composer.json file but composer checks repository version.. so waiting it to be potentially commited, you can use this in your composer.json project require :
"dompdf/dompdf":"v1.0.2 as 0.8.6"
Julien
Comment #3
ey commentedComment #5
neograph734The provided patch does not move dompdf to 'suggest' as proposed in the issue summary.
Also dompdf is the only PDF generation solution that does not depend on binaries to be installed. I personally like it being automatically installed because this is the most out-of-the-box experience this module can have.
Comment #6
welly commentedThere is an issue with this being a requirement in that the version of dompdf being installed is old and out of date, and also means other modules that have a dependency on dompdf are not able to be updated as the dompdf version is being locked by this module. I would back the suggestion to move dompdf to the suggest section.
Edit Have seen that the latest version of entity_print does support the latest dompdf verson so this should be fine. But it could still be an issue when different modules have different dependency version requirements.
Comment #7
larowlanThe current release allows v2, so we can probably close this?
Comment #8
heddnI think this is fixed. composer.json no longer mentions a requirement but only a suggest.
Comment #10
scuba_flyThe current v2 branch still has a requirement in. Not sure of that is put back in the last 3 months? At least the version constraint is now correct.