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 Ticket Printing - Bulk | Event Espresso - Staging Server
Hi there, I have created an event with seating chart (https://www.tamilaustralian.com.au/booking/events/?ee=22). We need to sell 1/2 the tickets via online and 1/2 via shops .. How can I block half the tickets and generate QR codes for it ? Thanks
The system is built for online registration rather than offline. However, what you could do is import X number of bogus attendees, and print off their tickets and sell those. The attendees can have the same name/email so you could use Tamil Offline or something (you can probably think of something better than I can!).
Having the attendees there will also reduce the attendee count.
Thats really the only way of generating the necessary QR codes.
Thanks – Can you elaborate this “However, what you could do is import X number of bogus attendees”. Can I create a CSV and import attendees under Attendees Report Page ( with their seat number ) ?
It does indeed work off of a CSV file, but you need to follow the structure so that it imports correctly.
Viewing 3 reply threads
The support post ‘Ticket Printing – Bulk’ 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.