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 Ticketing and Custom Template | Event Espresso - Staging Server
I have the latest versions of EE and ticket add-on. I wanted to customize layout a bit and followed the instructions of copying “template” folder into “wp-content/uploads/espresso/tickets”. I made my customization and nothing worked.
I reviewed the instructions a bunch of times but it still would not see the customized template I made. So I ended up just modifying the original index.php in the ticket template folder file within the plugins folder.
I know that any new updates will override my file but I could not get it to work the proper way. Is it possible you could review your instructions and make sure they are correct? I would prefer to have an override if possible.
I have customizations within the “wp-content/uploads/espresso/” already that work fine but for some reason the “tickets” folder is not recognized.
Also I played with permissions on tickets folder thinking that may have been an issue but again nothing worked.
Did you follow the PDF guide in the Ticketing addon directory? If so, my apologies, there is a typo in there that can confuse people. It is due to be removed from the addon altogether.
The correct directory structure is wp-content/uploads/espresso/tickets/templates/ and it needs to have a blank index.php file in there, which is why the guide advises to copy the entire templates directory from the add on to the tickets directory
I also just updated it a bit to make it clearer about the directory structure.
Viewing 1 reply thread
The support post ‘Ticketing and Custom Template’ 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.