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 Multilingual Event Espresso | Event Espresso - Staging Server
Not formally no, though some users have had success with using WPML and Event Espresso together. The plugin is translatable but some areas may require tweaking to get working with WPML.
Translation occurs via WordPress. So long as WordPress is in another language than US English and the correct Event Espresso language files are installed then Event Espresso will translate automatically.
That’s where the issues lie, those are not transaltable by WordPress, so it is up to the translation plugin such as WPML to resolve it. Some users prefer to set duplicate events, one in either language, and honestly I’m not sure how others have managed it.
IT may become easier once Event Espresso version 4.0 is out and stable, as it uses true Custom Post Types, which may make it easier to use plugins like WPML.
You could add a switch statement to each template file. Something like:
switch ($event_id) {
case 2:
case 4:
global $sitepress;
$sitepress->switch_lang("en");
break;
default:
}
I have to admit, I don’t have any experience using WPML. If you want a event title and description to be in a particular language, why not just write it in that language in the event editor. Or is it a matter of telling WPML what language you did write it in?
If you are trying to use multiple translations of EE, then you can take a look in espresso.php line 285, where we are setting the EE translation file to use based on the WPLANG constant. You could probably change that to pick up the lang from however WPML sets what the current lang is.
Viewing 7 reply threads
The support post ‘Multilingual Event Espresso’ 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.