You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using Open Source Point of Sale, which depends on this addon to print to a star receipt printer. We are using Windows 7. Recently, cashiers could no longer print to the ticket printer anymore, but, when I logged in to the PC as Admin, I had no problems. If I re-select the printer as Admin in the Non-Admin PC account, it works. But, if the computer is turned off, then the next day when they start it up again and go to the POS, it won't print again. If I clear out all sessions and cookies in the browser and log in again to the POS in the Non-Admin account, it won't print again. So, I am assuming the sessions are expiring overnight.
It appears to be a permissions issue, since I have no problem in the Admin account for the PC. Occasionally, cashiers will get the message at the top of the browser asking the user to allow a program to set printer settings when they first go to the POS, but not always. The issue is that the cashiers are not computer literate and ignore this message or close it out. They are volunteer retirees and it's tough to learn em anything.
Can someone explain why this is the way it is? What can I do to make jsprintsetup work dependably for all?
The text was updated successfully, but these errors were encountered:
The blocking usage of jsPrintSetup can be possible source for problem.
You can grant manually permissions for your host which is hosting application (mypos.example.com) to use jsPrintSetup.
To do this you have to:
Login in PC as regular user (to modify their FF profile)
Start Firefox and go to Add-ons
Click 'Options' of jsPrintSetup
Click 'Site permissions' on dialog
Add your host as 'Allowed' in list and save changes
Thank you for your reply and the information. I tried disabling jsprint and re-enabling it. Now, everything seems to be working. Should have tried this early on, so simple.
From: Dimitar Angelov <[email protected]>
To: edabg/jsprintsetup <[email protected]>
Cc: lkwetter <[email protected]>; Author <[email protected]>
Sent: Monday, October 2, 2017 12:45 AM
Subject: Re: [edabg/jsprintsetup] Addon disabled for non PC Admin accounts (#50)
The blocking usage of jsPrintSetup can be possible source for problem.
You can grant manually permissions for your host which is hosting application (mypos.example.com) to use jsPrintSetup.
To do this you have to:
- Login in PC as regular user (to modify their FF profile)
- Start Firefox and go to Add-ons
- Click 'Options' of jsPrintSetup
- Click 'Site permissions' on dialog
- Add your host as 'Allowed' in list and save changes
I hope that this will resolve your problem.—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
| | Virus-free. www.avast.com |
I am using Open Source Point of Sale, which depends on this addon to print to a star receipt printer. We are using Windows 7. Recently, cashiers could no longer print to the ticket printer anymore, but, when I logged in to the PC as Admin, I had no problems. If I re-select the printer as Admin in the Non-Admin PC account, it works. But, if the computer is turned off, then the next day when they start it up again and go to the POS, it won't print again. If I clear out all sessions and cookies in the browser and log in again to the POS in the Non-Admin account, it won't print again. So, I am assuming the sessions are expiring overnight.
It appears to be a permissions issue, since I have no problem in the Admin account for the PC. Occasionally, cashiers will get the message at the top of the browser asking the user to allow a program to set printer settings when they first go to the POS, but not always. The issue is that the cashiers are not computer literate and ignore this message or close it out. They are volunteer retirees and it's tough to learn em anything.
Can someone explain why this is the way it is? What can I do to make jsprintsetup work dependably for all?
The text was updated successfully, but these errors were encountered: