To resolve printing issues in Manager, I finally got around implementing PDF generator (starting with version 16.10.9). This means, clicking on PrintPDF button will generate PDF internally within Manager rather than showing Print dialog of underlying operating system which was causing a lot of issues (inconsistency, missing repeating headers, blank pages, crashes etc.)
I want to make sure all PDF documents generated in Manager look perfect before this capability is used by Email button as well (currently Email button uses external web-service to generate PDF which is slow and cumbersome).
I’m excited to see this finally in Manager. Not only it’s going to fix all printing issues. It opens a lot of possibilities too.
Faster emails & better security (your PDFs are generated locally instead of using external web-service)
Batch printing & emailing (e.g. print or email customer statements to all customers at once)
Compilation reports (create report pack with cover page)
Better support for headers & footers (e.g. adding page numbers)
Also without Manager being able to generate PDFs locally, I was delaying to release ability to customize HTML for all printed documents (currently available for invoices only). The main reason was that I didn’t want businesses to invest too much time into HTML customization before I know what HTML/CSS subset will be eventually supported.
How to test
Open screens where PrintPDF button is shown, e.g. any report.
As you can see Profit and loss statement looks pretty decent.
If you find instance where generated PDF is not good (disorganized, unprofessional, missing headers), post screenshot (you can censor private information within screenshot).
I’m thrilled to read that you are tackling the PDF process, but this last version is pre-alpha. I lost all printing capability when I installed it, except for one invoice that managed to pop up about 30 seconds after I clicked Print, and the columns were all odd sizes.
I urge you to withdraw v.16.10.9 or to release another version with legacy printing restored. This might be one instance where, for the sake of testing, you release a dev version and let people play with it on sandboxed data, rather than sending a non-working version out into the real world in production environments.
I was lucky tonight in that I had made a backup just before updating to 16.10.9, that I save copies of all my old Manager setup executables, and that I didn’t do any real work in 16.10.9 before recognizing that it’s broken. I was able to revert to 16.10.6 safely on my production machine.
Perhaps when the PDF button is click a warning dialog box appears stating this under development and printouts may not be correct - use Print button instead - click continue