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 Updating the language files | Event Espresso - Staging Server
In the past I had made custom edits to the .po and .mo language files to have everything display as I need it to. After the recent update I cannot locate the language files in the languages folder. After reviewing the update change log there is a clause that says that language files are being uploaded from the github repositories. Is it no longer possible to edit these files?
We are now side loading the language files into the wp-content/uploads/espresso/languages/ directory. So you can make your changes and they won’t get lost.
You can drop that function into custom_functions.php, add your text string changes, save, and Bob’s your uncle – you’ve changed text strings without creating a new language file or modifying templates/core files.
I notice that in wp-content/uploads/espresso/languages there are no language files and only the index.php file exists. Do I upload my existing .mo and .po files to the languages directory? Are they automatically detected there?
I notice that in wp-content/uploads/espresso/languages there are no language files and only the index.php file exists. Do I upload my existing .mo and .po files to the languages directory? Are they automatically detected there?
Yes. As of 3.1.30, Event Espresso will look in the /uploads/espresso/languages directory first then check the plugin’s languages directory. So you can upload language files there if you want. Note that it’s only the .mo file that’s actually used by WordPress. The .po files are what get edited in Poedit and generate the .mo file so you don’t strictly need to upload both.
The support post ‘Updating the language files’ 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.