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 Calendar's days and months' translation after update | Event Espresso - Staging Server
I have just updated the calendar, and the days and months are in English (my previous translations have been overridden). In the previous version, I could do the translation in the calendar’s settings; this is not the case after the update.
The problem is, my language files .po/.mo are in the uploads files (to avoid overwritting when updating), where I corrected many mistakes. I cannot find the days’ names in these files to translate them.
In the previous version of the calendar, days’ and months’ names were placed in the calendar’s settings (it is there that I could translate them).
I understand this. However, I cannot overwrite the .mo/.po files because I would lose all my corrections and modifications.
I suppose the solution is to indicate me the exact file in which the days and months are placed now and I add them to my .po./.mo files and translate them. Or perhaps is there any other solution?
The gettext solution works… until some word with accents is needed. It doesn’t accept words with accents, so for many languages this is a problem. There is also a small problem with the word “All-Day” in the calendar, which does not change although I have translated it with the gettext solution.
In which file are exactly situated the names of days and months and the word “All-Day”?
The support post ‘Calendar's days and months' translation after update’ 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.