Browser print menu option won't print properly #385
Replies: 3 comments
-
|
Might be related to this issue: In line 63 of latest includes/header.php
|
Beta Was this translation helpful? Give feedback.
-
|
Hi Ricard, As I recall the change to the print.css was an attempt to make some inquiries that didn't have a print option, format OK when sent to the printer. From what you say it clearly it makes other screens worse. With the use of DomPDF there are better ways now of printing an inquiry, so I'm happy for you to revert to the older print.css if that works for you. Likewise with $AutoPrintPage. It was intended as a way of a user printing stuff off without filling their computer up with PDF of sensitive information. DomPDF doesn't automatically save to disc so this no longer really applies either. Thanks |
Beta Was this translation helpful? Give feedback.
-
|
Hi Tim: Thanks for the details. I already reverted my install to the previous print.css, but I guess everybody would benefit from it (understanding its limitations and "ugly" output. I am happy to revert the file in master branch if nobody raises his hand against it in a few days time. $AutoPrintPage: I see... We can also remove these 2 lines of header.php if they have no use. Few years ago I started using WebClientPrint https://www.neodynamic.com/products/printing/raw-data/php/ for silent printing (the POS prints the customer receipt automatically, with no printing window). Works good and the licence price is correct. I am willing to share the integration if anyone finds it helpful, once we are done and dusted with v5 release. Thanks, |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi all:
We don't use much the browser option to print except for pages that we need a fast print-out and no webERP native PDF is available.
If you go to any page in webERP, right click and select the “print” menu option from the browser, webERP will either:
But, surprisingly, found a much better behaviour if using the css/print.css file from 20th oct 2018 (previous version to the current one). It prints all relevant data, just a bit ugly, though.
Same behaviour in Chrome, Firefox and Edge.
Is anyone else experiencing the same issue?
Thanks,
R
Beta Was this translation helpful? Give feedback.
All reactions