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 mo files and glotpress | Event Espresso - Staging Server
I found some translations in my current EE3 that are incomplete or incorrect (in Dutch). And I want them right. So I asked for a translation permission.
I’ve been reading about these translations. From what I understand EE3 uses Glotpress.
Question 1: I don’t understand why the translation in Glotpress is correct
First Name Voornaam
And on my site it is not correct? http://www.sintjansberg.be/event-registration/?ee=1
(it still says ‘First Name’ instead of ‘Voornaam’)
Doesn’t it take the PO file from Glotpress?
Question 2: I’ve created my own .mo file using poedit and uploaded it to wp-content/uploads/espresso/languages
What does it take now for the plugin to use that particular file?
I named it event_espresso-nl_NL.ENCODING.mo
I don’t see my updates in the website.
ok, got it. mo files and questions can be translated now.
thank you.
Viewing 7 reply threads
The support post ‘mo files and glotpress’ 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.