How to Reset WebClientPrint Protocol Handler on Chrome

Each time that WCPP client utility must be launched at the client machine, Chrome displays to the user a dialog asking for confirmation. The user is allowed to “Remember my choice”. If user check the “Remember my choice” option and click on “Do Nothing” or “Deny” or “Don’t open” button, then WCPP will not be launched making printing process impossible to be accomplished, nor WCPP detected or being able to send list of installed printers as well.

To revert back this Chrome setting, user must do the following:

  1. Open Chrome and go to the target website. Then click on “More” icon, then select “More tools > Clear browsing data…”. The option “Cookies and other site data” should be sufficient. Click “Clear Browsing Data” and Refresh the page. Chrome should display the URL Handler dialog again.
    If this process did not work, then try the next approach.
  2. If #1 option failed, they try the following.

    For Windows Clients
    – It’s mandatory to Quit Chrome (all instances).
    – Open Windows Explorer and go to your C: drive, then Users -> (your user profile name) -> AppData -> Local -> Google -> Chrome -> User Data

    NOTE: AppData is often a hidden folder, so be sure you can view “Hidden Items” if you will be looking for the file through your directory. (Click on the “View” tab and make sure the box next to “Hidden Items” is checked.)

    – Open the Local State  file by using Notepad.
    – Within the file, hit the keys Control and F to search for “webclientprint” (you could found “webclientprint3“, “webclientprint4“, etc depending on the version installed on that machine). You should see a line that says “webclientprint”: true
    – Delete true and replace it with false.
    – Save the file.
    – Re-open the file, and verify that the “webclientprint” line has been changed.
    – Now re-start Chrome

    For Mac Clients
    – It’s mandatory to Quit Chrome (all instances).
    – You will need to find and open the Local State file. Open a Finder window, and go to Library -> Application Support -> Google -> Chrome, and find the Local State file.

    NOTE: the Library folder may be hidden. To find it, right click on the Finder icon and select Go to Folder… enter “~/Library”

    – Once you’ve found the Local State file, double-click to open it using TextEdit.
    – Within the file, hit the keys Command and F to search for “webclientprint” (you could found “webclientprint3“, “webclientprint4“, etc depending on the version installed on that machine). You should see a line that says “webclientprint”: true
    – Delete true and replace it with false.
    – Save the file.
    – Re-open the file, and verify that the “webclientprint” line has been changed.
    – Now re-start Chrome

    For Linux Clients
    – It’s mandatory to Quit Chrome (all instances).
    – You will need to find and open the Local State file. Open File Explorer, and go to ~/.config/google-chrome/, and find the Local State file.
    – Once you’ve found the Local State file, open it using your favorite Text Editor.
    – Within the file, hit the keys Control and F to search for “webclientprint” (you could found “webclientprint3“, “webclientprint4“, etc depending on the version installed on that machine). You should see a line that says “webclientprint”: true
    – Delete true and replace it with false.
    – Save the file.
    – Re-open the file, and verify that the “webclientprint” line has been changed.
    – Now re-start Chrome

 

In case of needing further assistance, please contact our tech support team.

Advertisements

Print ESC/POS commands from ASP.NET right to the client printer

We’ve just published a new article about How to print raw ESC/POS commands from ASP.NET directly to the client printer that shows you how to get fast printing outputs with dot-matrix, impact, thermal or inkjet printers that support ESC/POS-compatible commands. The article shows you how to create ESC/POS commands for a simple receipt and how to get it printed from ASP.NET right to the client printer. Works with any popular browser (Chrome, IE, Firefox, Safari, Opera) on Windows, Linux or Mac!

 A Sample Receipt printed from ASP.NET and created by using ESC/POS commands

WebClientPrint 2.0 for PHP just released!

We’re proud to announce v2.0 of our WebClientPrint for PHP solution!

WebClientPrint allows you to easily send raw data, text and native commands to printers installed at the client machine without showing or displaying any print dialog box from PHP websites!

In addition to print raw printer commands, you can also print most common file formats like PDF, TXT, Word DOC, Excel XLS, JPG/JPEG, PNG, multipage-TIFF, and more!

WebClientPrint for PHP is a plug-in free solution based on jQuery and works with Windows, Linux & Mac clients through most popular browsers i.e. Internet Explorer, Firefox, Chrome, Opera and Safari!

Try the new WebClientPrint for PHP online and download a fully-functional evaluation version

For any tech questions please contact our engineers at http://www.neodynamic.com/support

WebClientPrint 2.0 for ASP.NET Update – Chrome 30 on HTTPS

We’re glad to announce a new update to WebClientPrint 2.0 for ASP.NET. This new update includes:

[Fixed!] Support for Chrome v30 when website is running under HTTPS protocol.

This update requires the installation of the server software only.

Download WebClientPrint 2.0 for ASP.NET server component

The “File version” values for this update are:

> Neodynamic.SDK.WebClientPrint.dll patched to v2.0.2013.1009

Print ASP.NET Local Reports RDLC without Preview or Print Dialog

You have an ASP.NET RDLC report and want to allow your users to print it without previewing it? Want to go further and print it without displaying any print dialog? And you want it to work with Internet Explorer, Chrome, Firefox, Opera & Safari? Take a look at our new article about How to Print an ASP.NET Local Report RDLC without Preview or Printer Dialog by using our WebClientPrint for ASP.NET solution

Feel free to contact our team for further assistance.

jQuery ajax request error Status 0 on SSL-HTTPS when using Opera or Safari

Today we were testing our WebClientPrint for ASP.NET vNext and found an issue with jQuery Ajax requests on HTTPS but just when using Opera or Safari as the code worked just fine with IE, Chrome & Firefox.

In short the issue was this. The URL we specified to jQuery $get() contained the port number for HTTPS which is 443. Something like this $.get('https://localhost:443/something.aspx', function (data) { ... });

Again, that code worked just fine with IE, Chrome & Firefox but when using Opera or Safari, the Ajax error was “Status 0”. Removing the port number 443 from the URL fixed the issue on those browsers. HTH,

How to print barcode labels to client-side Zebra thermal printers from ASP.NET

Print barcode labels to users’ Zebra thermal printers from ASP.NET (or any web server technology) is not an easy task. There are a couple of ways to try out but all share this workflow:

  1. User enters the webpage using his favorite browser (IE, Mozilla Firefox, Google Chrome, Opera, etc.)
  2. The webpage displays the barcode label in some “format”, let’s see:
    1. No Plugin approach:
      • A simple HTML markup with <img> tags for barcodes and other common tags for text
      • One single <img> tags where the barcode and text is on it
    2. Plugin approach:
      • A PDF file containing the barcode and text
      • A Flash swf file containing the barcode and text
      • A Silverlight applet containing the barcode and text
  3. User prints the barcode label depending on the approach used in #2:
    1. For No Plugin approach, the “print page” functionality of the user’s browser is in charge.
    2. For Plugin approach, the “printing API” of the selected plugin platform (Adobe PDF Reader, Flash or Silverlight) is in charge.

Each of the above combinations has its pros and cons, for instance:

  • No Plugin approach
    • Pros: it does not require the user to have installed any Plugin on his machine
    • Cons: because this approach leverages the “print page” functionality of the user’s browser, it requires lots of effort from both, the developer and the user, to configure and fine tune all stuff to get barcode label content correctly printed on thermal printers
  • Plugin approach
    • Pros: in general, the “printing API” provided by the Plugin is more rich and customizable from the developer perspective. This allows the barcode label content to be correctly printed on the user’s thermal printer with almost any intervention or configuration from the user.
    • Cons: the user is forced to install the selected Plugin on his machine. Note: this is not always a restriction because Acrobat PDF Reader or Flash are widely installed out there.

Well after some tests here at Neodynamic, we have found the Plugin approach using Adobe PDF to be one of the most reliable ways to get your barcode labels printed on user’s thermal printers accurately. We have just published a guide providing some sample code about this topic using our ThermalLabel SDK 4.0 in ASP.NET client-side printing scenarios

kick it on DotNetKicks.com