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 PDF version of Custom Ticket strips out styling | Event Espresso - Staging Server
Hi, I’m not sure if I’m missing something; my Custom Ticket displays beautifully in the browser, but when I download the PDF, all styling is stripped out. The styling looks horrible, and the positioning is also lost. I tried tables, but that didn’t work either. It isn’t a browser issue (I also downloaded the PDF and viewed it in Acrobat). Is there a way to style the custom tickets so at least some of the look and feel is retained in the PDF? I would appreciate any guidance.
Hi Dean, thanks, but I played around with it and discovered there were two issues:
1. The development site was password-protected; this prevented the stylesheet from being interpreted correctly when converting to PDF. I removed the password and the styling displayed.
2. The styling is tricky in any case, particularly with tables and widths. I just tweaked and compromised until something reasonable appeared.
Hopefully that’s of use to someone else!
Viewing 2 reply threads
The support post ‘PDF version of Custom Ticket strips out styling’ 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.