Fix dev/core#2959: some PDFs hard-code format to "a3 landscape", overriding default PDF format #22098
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
See the original issue at https://lab.civicrm.org/dev/core/-/issues/2959. In short: civicrm normally specifies default pdf format according to whatever is configured in the UI (if any). But in some cases it is hard-coded to use "A3 Landscape" -- e.g. when calling an existing CiviCRM URL with "?snippet=3" in order to generate a pdf. (We're doing this on some sites in order to print Event Participant Listings as PDF file.)
This happens because there's actually code in CiviCRM that says "use A3 Landscape", and this code is invoked in workflows like described above.
Before
After
Tech details
Hard to guess why this code was written in the first place (esp. since it predates SVN-to-git migration, see it in 6a488035). It seems fairly uncommon to keep A3 paper in the printer by default.
Comments
I've at least got a "sounds good" from @jaapjansma in the issue comments: https://lab.civicrm.org/dev/core/-/issues/2959#note_67495