If you are desperate to do server-side printing with PHP on a *nix machine then you can always use the fsockopen() function and send a pre-build PJL (Printer Job Language) string directly to the printer. As long as your printer supports PJL then there should be no problem. Just also bare in mind that unless you are doing something very special, like sending the print job to a remote printer and not the printer the client is at you should just make a report page generated by php and apply a css stylesheet which makes the page styled for printing.
printer_open
(No version information available, might be only in CVS)
printer_open — Opens a connection to a printer
Описание
resource printer_open
([ string $printername
] )
This function tries to open a connection to the given printer.
printer_open() also starts a device context.
Список параметров
- printername
-
The printer name. If no parameter was given it tries to open a connection to the default printer (if not specified in php.ini as printer.default_printer, PHP tries to detect it).
Возвращаемые значения
Returns a printer handle on success or FALSE on failure.
Примеры
Пример #1 printer_open() example
<?php
$handle = printer_open("HP Deskjet 930c");
$handle = printer_open();
?>
printer_open
knightcon at bluebottle dot com
15-Dec-2006 02:04
15-Dec-2006 02:04
jt at jtis dot de
31-Aug-2004 12:39
31-Aug-2004 12:39
Revision: Single quotes DO work, but with a triple slash, like
printer_open('\\\SERVERNAME\PRINTERNAME');
Weird.
jasonlam_ at hotmail dot com
05-Jun-2003 01:22
05-Jun-2003 01:22
Connecting to Network Printers
<?php
$handle = printer_open("\\\\DOMAIN_NAME\\Printer_Name");
?>
Similiar to how you would locate a domain on your network
you need to have 2 prefix slashes. But as reminder
you need to escape it. So really you need 4 slashes. It
worked me. Hopefully this helps who is having problems
connecting to network printer.
csammis at iastate dot edu
01-May-2002 04:38
01-May-2002 04:38
As stated on the index page for all the printer functions, these are supported under Win32 *only*...in fact, they're frontends API calls. I'd go ahead and say that they would probably never be ported to *nix because of the many various ways of handling printers. Windows, for all its faults, at least has a unified printing system.
As to editing the php.ini, try it with no path at all, like the first example here
