Print-Time Prompt Not Showing On Clients
I have used BarTender to create labels with db query prompts, and those work beautifully from the Web Print interface. Now I'm trying to create a simple label with just a text box and a print-time prompt to enter text so users can make labels for things that are not in the database.
I have a single label with a single text box. I have set up a print-time prompt in the text box properties, and I've enabled "Show Prompt Panel" in the Panel Visibility section of the Site Administration page of the Web Print Server. When I go to Label Format Selection on the server that hosts BarTender and choose my new label, I see the Prompt Dialog I created, and I can enter text and successfully print the label. However, when I choose the same label on a client machine (same version of the same browser), the Prompt Dialog box is missing from the page. If I hit the Print button, a label prints with my sample text, but I'm never able to enter my own text.
Does anyone have any idea what I'm missing here? My simple label is proving other than simple today.
I have a single label with a single text box. I have set up a print-time prompt in the text box properties, and I've enabled "Show Prompt Panel" in the Panel Visibility section of the Site Administration page of the Web Print Server. When I go to Label Format Selection on the server that hosts BarTender and choose my new label, I see the Prompt Dialog I created, and I can enter text and successfully print the label. However, when I choose the same label on a client machine (same version of the same browser), the Prompt Dialog box is missing from the page. If I hit the Print button, a label prints with my sample text, but I'm never able to enter my own text.
Does anyone have any idea what I'm missing here? My simple label is proving other than simple today.
0
-
As a follow-up, I'm still not sure what caused the issue, but a reboot of the Web Print Server seems to have solved it. 0 -
Good to hear that you got it running okay. Difficult to say what might have gone wrong, but I guess something somewhere was hung up. Restarting the web site might have done the trick also. 0
Please sign in to leave a comment.
Comments
2 comments