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 How to Customize The Printed Ticket... | Event Espresso - Staging Server
The template file is the index.php file included with the ticketing add-on. It’s best to copy this over to /wp-content/uploads/espresso/ and work on a copy so you don’t lose your changes when the ticketing add-on gets an update. Here are the basic steps to set up a custom template:
1) Create a new folder in /wp-content/uploads/espresso/ and name it tickets
2) Copy over the entire /templates folder from the ticketing add-on plugin into this new folder. So it will look like this: /wp-content/uploads/espresso/tickets/templates
3) Make a duplicate of the index.php file in this new folder and rename it to something like custom.php
?4a) Modify custom.php using html and the template short tags listed in the ticketing documentation.
4b) Create and modify a new css stylesheet if need be
5) Create a new ticket template and select this new template/stylesheet combo in the ticket template manager
6) Select this ticket template for the events in the “Custom Tickets” box of the event editor.
This reply was modified 12 years, 3 months ago by native alien.
Viewing 3 reply threads
The support post ‘How to Customize The Printed Ticket…’ 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.