Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot create PDF when Unassigned classification is selected #4552

Closed
crossan007 opened this issue Nov 29, 2018 · 1 comment
Closed

Cannot create PDF when Unassigned classification is selected #4552

crossan007 opened this issue Nov 29, 2018 · 1 comment

Comments

@crossan007
Copy link
Contributor

crossan007 commented Nov 29, 2018

On what page in the application did you find this issue?

Reports/DirectoryReport.php

What version of ChurchCRM are you running?

3.0.12

==> /home/churchcrm/public_html/logs/2018-11-29-php.log <==
[28-Nov-2018 23:02:07 America/New_York] PHP Fatal error: Uncaught Exception: FPDF error: Interlacing not supported: /home/churchcrm/public_html/Images/Person/1.png in /home/churchcrm/public_html/vendor/setasign/fpdf/fpdf.php:271
Stack trace:
#0 /home/churchcrm/public_html/vendor/setasign/fpdf/fpdf.php(1296): FPDF->Error('Interlacing not...')
#1 /home/churchcrm/public_html/vendor/setasign/fpdf/fpdf.php(1262): FPDF->_parsepngstream(Resource id #12, '/home/churchcrm...')
#2 /home/churchcrm/public_html/vendor/setasign/fpdf/fpdf.php(885): FPDF->_parsepng('/home/churchcrm...')
#3 /home/churchcrm/public_html/ChurchCRM/Reports/PDF_Directory.php(484): FPDF->Image('/home/churchcrm...', 13, 37, 20)
#4 /home/churchcrm/public_html/Reports/DirectoryReport.php(330): ChurchCRM\Reports\PDF_Directory->Add_Record('Admin, ChurchIn...', '\n', 1, 0, '1')
#5 {main}
thrown in /home/churchcrm/public_html/vendor/setasign/fpdf/fpdf.php on line 271

@crossan007
Copy link
Contributor Author

This works if I delete the 1.png image from my server:
1

I think this was included in previous versions of ChurchCRM, but doesn't seem to be in the current codebase (deployments), so I don't think this really needs a code fix - people should just delete this image.

All other (supported) pathways for image uploads will ensure proper image format.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant