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 Customizing Ticket | Event Espresso - Staging Server
I’m stuck, and hoping someone can shed some light :)
I can’t seem to get any changes to the .css files to show up.
I’ve moved the files to the uploads/tickets/templates folder. I have selected the desired css and php files in the ticket template. I also have the custom ticket selected in the event.
The changes in the .php files are showing up, just none of the styles are there. Am I missing something? Even the stock red.css and simple.css files don’t work.
What files I’m looking at:
uploads/espresso/tickets/templates/index.php
uploads/espresso/tickets/templates/custom.php [new file i created by duplicating index.php]
uploads/espresso/tickets/templates/css/base.css
uploads/espresso/tickets/templates/css/simple.css
uploads/espresso/tickets/templates/css/red.css
uploads/espresso/tickets/templates/css/custom.css [new file i created by duplicating simple.css]
Bingo! Seth, you rule! I knew i was missing something obvious! <3 That was my problem!
Thank you so much for the fast response! Support Forums can be hard to get answers on, so I appreciate your quickness!
Viewing 5 reply threads
The support post ‘Customizing 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.