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 Printing Specifications | Event Espresso - Staging Server
Guys, I have a Boca Printer that I want to use to link up physical tickets with EE. I know EE wasn’t initially designed to support printing tickets in bulk, but from my understanding after reading through forum, their is a way to kind of get around it by registering a set amount of tickets as “Physical Ticket” so we can capture a unique QR Code and print out a set amount at one time. Is this doable? Also, Please let me know if the software requires the FGL or PCL printer language and if the printer needs to be configured for 200 or 300 DPI. I could not find anything in the documentation describing this. Thank you
You can create X number of fake attendees thus X number of tickets, that in itself is a reasonable job as we have the import attendee via spreadsheet add on in the Pr release.
Printing them off though will be a very manual job as you will need to go into each attendee, click the ticket link and print from there.
“FGL or PCL printer language and if the printer needs to be configured for 200 or 300 DPI”
The tickets are designed to be printed from a home printer via the browser, so I am not sure that FGL/PCL is relevant and the DPI is dependant on the users settings.
Sorry I can’t be much more help, but as you say, the system isn’t designed for bulk offline printing.
Viewing 1 reply thread
The support post ‘Printing Specifications’ 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.