[#69625] Error in PDF exports if font file storage is broken #21345
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
as-op
force-pushed
the
bug/69625-error-in-pdf-exports-if-font-file-is-damaged-or-storage-is-broken
branch
from
541ff11 to
c015499
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Ticket
https://community.openproject.org/work_packages/69625
What are you trying to achieve?
A custom font file is uploaded, but its storage is broken.
Instead of a pointless
The PDF export could not be saved: undefined method 'body' for nilmessage, the export should continue without the font applied.What approach did you choose and why?
CustomStyle.current.export_font_regular.local_file.present?)Merge checklist