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 Translation php code cleanup | Event Espresso - Staging Server
After installing “Codestyling Localization” and scanning the source files of Event Espresso 3.1.36.P, there were several problems encountered, which should be cleaned in EE php source files:
1. multiple text domains are used, besides ‘event-espresso’; probably it is unintentional, the list being composed of:
twentyten, event_espress, debug-bar, default
These strings totaling 61.
2. Strings which you add in newer EE versions take a while to get to GlotPress. Currently, there are about 66 strings (except the 61 above) which are part of ‘event-espresso’ text domain, but are not present on GlotPress. This leads to delays in translation availability.
3. String ‘Add Additional Attendee’ is present in the source code as __(‘Add Additional Attendee’, ‘event_espresso’), but on GlotPress there is no sign of this, is this the effect of no. 2.?
Is it possible that you fix point 1. in the next EE 3 release version? I am planning to launch in the next weeks and this translation issues are keeping me blocked.
I am willing to give you all my support for this task, it a simple translation task like:
The support post ‘Translation php code cleanup’ 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.