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
Strict Standards errors? | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Strict Standards errors?

Strict Standards errors?

Posted: March 25, 2014 at 12:54 pm

Viewing 1 reply thread


lhammond

March 25, 2014 at 12:54 pm

I am doing some testing in my development site, and saw these errors in the registration process. They don’t show in my live site because I’m not displaying errors on the screen there, and they don’t seem to actually indicate a problem with registration. But I was wondering, will future EE updates be made to meet the Strict Standards requirements, or have they already perhaps been addressed? Will these errors go away or do I need to do something about them? I’ve got EE Version 3.1.35.1.P and MailChimp integration Version 1.1.

<code>Strict Standards: Non-static method MailChimpController::list_subscribe() should not be called statically in /public_html/development/wp-content/plugins/event-espresso/includes/process-registration/add_attendees_to_db.php on line 431

Strict Standards: Non-static method MailChimpController::get_mailchimp_list_id_by_event() should not be called statically in /public_html/development/wp-content/plugins/espresso-mailchimp/mailchimp.controller.class.php on line 239

Strict Standards: Non-static method MailChimpController::get_valid_mailchimp_key() should not be called statically in /public_html/development/wp-content/plugins/espresso-mailchimp/mailchimp.controller.class.php on line 242</code>


Anonymous

March 25, 2014 at 1:21 pm

Hi lhammond,

But I was wondering, will future EE updates be made to meet the Strict Standards requirements, or have they already perhaps been addressed?

Some of these will be addressed in future versions, some already have been.

Will these errors go away or do I need to do something about them?

I’m guessing you are running PHP5.4, later versions of PHP are moving towards stricter standards so previously valid PHP code is now throwing errors such as those. You do not need to do anything yourself, other than disable error reporting for the time being.

Hope that helps.
Viewing 1 reply thread

The support post ‘Strict Standards errors?’ 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.

The original Forum description...

Status: closed

Updated by Anonymous 10 years, 10 months ago ago

Topic Tags

Tagged: 

Notifications

This topic is: not resolved
Event Espresso - Staging Server