This one was not discussed during the usergroup tour, and I have not seen anyone mention it since we released the CF8 public beta, so ...
If you've ever needed server-side printing under programmatic control, ColdFusion 8 introduces a new <CFPRINT> tag. <CFPRINT> prints PDF files (including those created using <CFDOCUMENT>, <CFREPORT> and <CFPDF>) to a printer of your choice. At a minimum, <CFPRINT> requires just the name of the PDF file to be sent to the default system printer, but additional attributes can be used to specify the printer, copy count, the pages to print, as well as to pass lots of other printer settings. The list of available printers (and their names, as must be passed to <CFPRINT>)is listed in the ColdFusion Administrator. And a new supporting GetPrinterInfo() function returns all sorts of information about specified printers.
While I don't claim to be Ben, I would imagine this is targetted to companies who host their own servers and want to print things like invoices, nightly reports, etc.
--- Ben
We use it to send a PDF print job to a "broadcast" printer that in turn prints out at 8 different workstation printers.
<cfprint type="pdf" pdf="mypdf.pdf" priner="Name Of Printer">
Nice, huh? ;-) I'd love for you to try it out, if you can, grab the beta and see if it works for you, and then let us know.
--- Ben
This great news, but...
...does cfprint have arguments for network authentification or would the instance of the CF windows service have to "log on as" an account that the printers' network server would permit?
- The user CF is running under has to have permissions to print.
- Works on all platforms that CF supports (and I've run tests on my Mac)
More in the CF Developers Guide.
HTH
Damon
now... with this, his wishes are answered :) yummies!
I wonder if there is a Custom Tag or Com object that would allow us to use <cfprint on CF 7, since we are not quite ready to put CF8 in our production environment...
--- Ben
--- Ben
--- Ben
Is this a bug or an undocumented cf standard edition limitation?
I use CF8 on Windows Server 2003 & IIS6
Thanks for your help!
Yesterday I decided to give-up with this tag when I discovered that with more than 1 page to print <cfprint> print all pages in one page! Another bug... another week lost to find a way to bypass the problem... NO THANKS!
<cfprint> was the main feature that convinced me to upgrade to version 8, but to solve my problems I need now to buy another software (I'M evaluating 3-Heights PDF Printer Service and seems to work very well...) and spend 1000.00 Euro to "finally" print something correct.
I hope that Adobe will fix these bugs as soon as possible.
Have you submitted the issues you are having as defects? Are you on the ColdFusion prerelease program? We'd love to fix the issues you're having, we just need to know what they are. :)
Happy New Years!
Jason
Is there a fix to this?
because I installed the network share printer in CF8...
but in coldfusion administrator It look cannot detec the printer i installed ?
Regards,
Dylan
Does CFPrint support parallel processing? By this I mean: two users on two different workstations process two different .cfm pages in their Internet browsers. Each .cfm page has a cfprint tag referring to two different printers. The first user is printing a very large document, and it takes several minutes for JRun (or whatever java controls cfprint) to process the request and send the entire job to the printer. In the meantime, the second user is staring at a blank screen with a "waiting for page blah2.cfm" message, until the first user's page completes. Is this serial-type behavior normal for ColdFusion printing or can I change a setting in the ColdFusion Administrator?
I suggest you research how print queue's work. What happens is that a print job is added to the queue of the printer attached to the server. When one job finishes the other starts.
in your case, you have two seperate printers, with two queues.
if you want to get around the second request waiting for the first, the docs have a suggestion on using CFThread http://livedocs.adobe.com/coldfusion/8/htmldocs/he... (see at the bottom of the page)
keep in mind it's nigh on impossible to get a message back saying that the printer failed because of lack of toner or paper jam or whatever, especially if it's kicked off by a web request.
on a .NET project I'm in we use a 3rd party add-on called EasyPDF (it cost a fortune!) - it was the only "ActivePDF" type-tool for .NET that we could find that could print to a physical printer hooked up to the server. it's the same story as above. BTW, if we could have used CF instead of .NET we would have got more work done, and with the CFPDF family of tags, saved ourselves a bit of money... go figure.
hope this helps
After playing around with cfthread, it seems that the threads only take priority over threads in the same page, not threads running on other pages. So when I run a print job on http://server1/page1.cfm and someone else runs http://server2/page2.cfm with cfprint inside cfthread with a HIGH priority, page2.cfm still waits for page1.cfm to finish. I need some way to manipulate ColdFusion's "print queue."
Anyone familiar with this phenomenon and how to correct or control it?
I was having the same type of problem, but it was with text not printing properly. It looked fine in the pdf, but cfprint garbled it up. This was on ColdFusion 8.0.1. We fixed it by applying the most recent jpedal patch - jpedal processes pdf pages for ColdFusion. Find the patch at http://kb.adobe.com/selfservice/viewContent.do?ext...
http://blog.monochrome.co.uk/2008/11/printqueue-pd...