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-Ticket - QR-Code and Umlauts fail | Event Espresso - Staging Server

Support

Home › Forums › Ticketing › PDF-Ticket – QR-Code and Umlauts fail

PDF-Ticket – QR-Code and Umlauts fail

Posted: May 8, 2013 at 1:00 pm

Viewing 2 reply threads


Marko Geisler

May 8, 2013 at 1:00 pm

Hey there,

when i use the html-view of the ticket, everything is fine

http://www.elbe-erlebnistoerns.de/?ticket_launch=true&id=215&r_id=44-518a81de77128&html=true

But when you click on “Download Ticket as PDF” / in German “Ticket als PDF herunterladen”, you see a lot of umlauts-errors in the pdf and the QR-Code is missing.

In both of them, html and pdf, the event dates were not translated, as you should read “16. Juni 2013” and not “16. June 2013”.

Best regards,
Marko


Marko Geisler

May 8, 2013 at 1:03 pm

Using EE-Version 3.1.32.P and Event Espresso Ticketing Version 2.0.10 :)


Josh

May 9, 2013 at 8:26 am

Hi Marko,

You might try swapping in the latest dompdf scripts from here:

https://github.com/dompdf/dompdf

they go into event-espresso/tpc/dompdf.
Viewing 2 reply threads

The support post ‘PDF-Ticket – QR-Code and Umlauts fail’ 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.

Status: closed

Updated by Josh 11 years, 8 months ago ago

Topic Tags

Notifications

This topic is: not resolved
Event Espresso - Staging Server