problem printing orders from terminals

[Allan]

My client is having a problem with printing shopsite orders from terminals. The note he sent me is below. He can print fine from is PCs, and other web pages print fine from the dumb terminals, just not the shopsite orders. Any suggestions? Thanks, Al

From my client...

We upgraded to new servers here. Now when we go into Shopsite orders, view all and then hit print at the bottom, nothing happens. This is at terminals (dumb terminals). It works okay at pc workstations. The default printer is correctly set on these terminals. You can see the orders on the screen and you can print from the IE print function (albeit without correct page breaks) but, on the terminals, you can’t print using the Print button. I see that it is some kind of cgi process where I guess it hunts for the default printer or something? No print dialog window comes up or anything. Any ideas?

[Jim]

ShopSite just uses the browser to do the printing, there is no special code to make this work. If your browser can print the page then it should work from within ShopSite.

[Allan]

Thanks for note. I went into the BO for my clients shopsite store and I took a look at the html for an view order and saw this code at the top of the page...

<style media="print">
.noprint { display: none }
</style>

and then this code at the bottom...

<input class="noprint" type=image src="https://www.boyerscoffee.com/media/en-US/buttons/print.gif" width="150" height="25" align="bottom" border="0" name="Print" alt="Print" onClick="window.print();return false;">
<input class="noprint" type=image src="https://www.boyerscoffee.com/media/en-US/buttons/ok.gif" width="150" height="25" align="bottom" border="0" name="View OK" alt="OK">


I'm not a CSS expert so I don't know what this code is for, but could it be related to the problem my client is having with printing from a dump terminal?

[BFChris]

All the CSS does is prevent unnecessary items (like the Alert Box at the top of the page and the print button at the bottom) from appearing on the PRINTED version of the page.

Unless a tag was improperly closed (hence expanding the noprint style around additional elements) it shouldn't affect the printout at all (other than preventing the unneeded stuff from printing).

[Jim]

javascript is required for the print to work so if your dumb terminals don't have javascript turned on that is probably the issue. Note that javascript being turned on is one of the expected features for the backoffice screens as javascript is used in many places.