Problem/Motivation

This module supports multiple PDF rendering engines. Therefore, dompdf should not be listed as required in the composer.json file.

"require": {
    "dompdf/dompdf": "~0.8.0"
  },

Steps to reproduce

Proposed resolution

Move dompdf to 'suggest' section so that it is not required. Furthermore, change the version requirement to "^0.8.0" so that newer versions can be used, e.g., to get latest fixes and PHP8 compatibility.

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

lunk rat created an issue. See original summary.

julien.sibi’s picture

Hi,

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

ey’s picture

Status: Active » Needs review

dan.d made their first commit to this issue’s fork.

neograph734’s picture

Status: Needs review » Needs work

The 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.

welly’s picture

There 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.

larowlan’s picture

The current release allows v2, so we can probably close this?

heddn’s picture

Status: Needs work » Fixed

I think this is fixed. composer.json no longer mentions a requirement but only a suggest.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

scuba_fly’s picture

The 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.