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
Ticket with wrong date localization | Event Espresso - Staging Server

Support

Home › Forums › Translations › Ticket with wrong date localization

Ticket with wrong date localization

Posted: January 15, 2013 at 11:48 am

Viewing 5 reply threads


Marko Geisler

January 15, 2013 at 11:48 am

Hey there :)

When a attendee generates his ticket, the date format uses the english names for months and days (e.g. 12. March 2012″ instead of a localized one, like the german “12. März 2012”).

It would be cool if that could be fixed, since i also have the older generation as a customer ^-^

Best regards, Marko


Dean

  • Support Staff

    •

January 16, 2013 at 4:36 am

Hey Marko,

Thanks for letting us know I will get that raised with the developers!


Marko Geisler

January 16, 2013 at 10:22 pm

In addition to that…

I noticed that EE displays the date on the general settings page (where u can check if your Time-/Date-Settings were correct) in the english language.

In the Event-Overview, there the monthnames were translated and time/date is correct.

If i want to edit an event, there the date for start/end of registration and start/end of the event, the date-format is “Y-m-d”, while it should be “d.m.Y”, at least here in germany :)

Speaking of editing the events… the cool jquery datepicker for choosing the date isn’t translated.

Regarding the Ticketing-Part, i think that one is a little mess for translators, since more than half of the strings were untranslatable written in the template-files. (See “Print this and bring it to the event”, “Download PDF”, or “Qty.” for the number of tickets.

If i can help you further by being more specific or providing more information, or if i can do something, please let me know :)

Best regards, Marko


Josh

January 22, 2013 at 3:34 pm

Hi Marko,

There are already a few tickets in our issue tracker (eg the datepicker pop up and adding an option to localize the date display)

We actually have an open ticket that we are working on for the ticket template to make it translatable. Can you verify whether anything is actually translating on the ticket template?


Marko Geisler

January 22, 2013 at 3:56 pm

Hey Josh, when i am remembering it correctly, i think there were at max 2 Strings translated, the others were hardcoded in the Template.

Looking in the direction of an dev, of you write me a Short Tutorial, i Think i can Convert the Strings myself to translatable ones. In Case you Think that is a cool idea, please send me an Email .

Best Regards, Marko


Josh

January 22, 2013 at 7:00 pm

Hi Marko,

We’re looking into adding support for translatable ticket templates. It’s more than a matter of adding translation functions to the example template, and there are shortcodes that may need to be refactored.

What I would suggest for now would be to directly translate the sample ticket template. I will look into a way of making that date shortocode pull from the date options set in the General WordPress options.
Viewing 5 reply threads

The support post ‘Ticket with wrong date localization’ 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.

Post any questions about the language files, translating Event Espresso, or issues with our GlotPress site for translations here.

Status: closed

Updated by Josh 11 years, 12 months ago ago

Topic Tags

Notifications

This topic is: not resolved
Event Espresso - Staging Server