dev/core#2028 Add in a status check for checking if the wkhtmltopdf p…

[seamuslee001]

…ackage is installed in the expected location, Also ensure if it isn't then the pdf generation falls back on the current default which is DOMPDF

Overview

As per the lab issue a fatal error can be generated when trying to send out a Participant confirmation if your attaching the PDF onto it and your using wkhtmltopdf according to the settings but the package isn't installed for some reason.

Before

Hard fail on PDF generation

After

Status check and a softer fail with a fallback to using DOMPDF

ping @eileenmcnaughton @demeritcowboy @monishdeb

[civibot]

(Standard links)

• If this is your first pull-request for CiviCRM, please browse CONTRIBUTING.md for information about the development and testing processes.
• If you are reviewing this pull-request, you may wish to consult the test sites and the Review Standards (long template, short template).

[demeritcowboy]

• General standards
  • [r-explain] PASS
  • [r-user] PASS
  • [r-doc] PASS
  • [r-run] PASS
• Developer standards
  • [r-tech] PASS
  • [r-code] PASS
  • [r-maint] ____
  • [r-test] Pending Pending latest run.

[colemanw]

I've always wondered... why do we need to store the path? Can't we look it up with a command like which wkhtmltopdf?

[seamuslee001]

@colemanw I presume because which not be on stuff like windows servers or similar or the package may not be in the system PATH

[demeritcowboy]

Good thought but it might not be in path. And on windows that would fail.

[demeritcowboy]

Oh oh we're starting to think alike.

[mxroo]

@mxroo would you be able to do a PR to apply that fix to this file?

Done. #19843

[agileware-justin]

Regression Gitlab, https://lab.civicrm.org/dev/core/-/issues/2478