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
PHP Notices | Event Espresso - Staging Server

Support

Home Forums Event Espresso Premium PHP Notices

PHP Notices

Posted: September 27, 2013 at 7:34 am

Viewing 3 reply threads


phgroup

September 27, 2013 at 7:34 am

Hello,

I am getting the following php notices since installing EE:

—————-
PHP Notice: Undefined index: every12hours in /wp-includes/cron.php on line 103

PHP Notice: Undefined index: every24hours in /wp-includes/cron.php on line 103

Undefined index: /wp-content/plugins/espresso-volume-discounts/espresso-volume-discounts.php on line 1289

PHP Notice: Use of undefined constant EVENTS_CATEGORY_TABLE – assumed ‘EVENTS_CATEGORY_TABLE’ in /wp-content/plugins/espresso-volume-discounts/volume-discounts-settings.config.php on line 150

PHP Notice: add_contextual_help is deprecated since version 3.3! Use get_current_screen()->add_help_tab() instead. in /wp-includes/functions.php on line 2900

PHP Notice: Undefined index: page in /wp-content/plugins/espresso-volume-discounts/espresso-volume-discounts.php on line 934
—————-

These seem like simple fixes, is there a chance your team could fix this? Please note: I don’t want to suppress errors for debugging purposes.

Thanks!


Anonymous

September 27, 2013 at 9:55 am

Hi phgroup,

I’ve raised a ticket to get these fixed although I can not comment on a time-scale unfortunately.


Josh

October 7, 2013 at 10:10 am

If you do not want to suppress errors due to debugging purposes it may be best to have these logged to a file before you go to production. There is some example code that can be used in the wp-config.php file here that you can use to make errors get logged to a file and not be displayed on the front end of the website:

http://codex.wordpress.org/Editing_wp-config.php#Configure_Error_Logging


phgroup

October 11, 2013 at 9:17 am

Josh,
Thanks for the response. They are getting logged to a file. I guess what I meant to say is I want to see errors (in the file) so I can catch other issues while developing, but it’s hard because event espresso is constantly generating these errors.
Thanks

Viewing 3 reply threads

The support post ‘PHP Notices’ 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.

Event Espresso - Staging Server