Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114 Support for ticket printers | Event Espresso - Staging Server
Does Event Espresso support real ticket printers, such as Boca Systems’ thermal ticket printers?
Is there more detailed information about the Ticketing plugin, than what is available on your web page?
Most of the pertinent answers during my search on your website seems to be blocked by your permission scheme, that requires my account to make a purchase of the license before I can see the information.
The ticket is produced in either html or pdf formats, and our template is designed to print on a standard 8 1/2 X 11 printer paper. You would need a new template to make it fit on that page size, and from what I could see on the Boca site, it looks like they require an FPL file format, which we do not produce. You might want to contact Boca and see if their printers will take a PDF format.
Your marketing videos and pictures show standard tickets, not 8.5 x 11 paper. Are you at least able to generate a pdf in the size of a standard ticket?
Yes, I was able, with a couple of modifications, to produce the pdf of the ticket to 2 inch by 5.5 inch. It will require a new ticket template to arrange everything on that size, but since the ticket pdf is a rendering of the layout produced by html and css, it’s something that a designer should have no problems with. Is your ticket printer able to handle a pdf input?
Viewing 4 reply threads
The support post ‘Support for ticket printers’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.