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
Upgrade to 3.1.27 triggers fatal error | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Upgrade to 3.1.27 triggers fatal error

Upgrade to 3.1.27 triggers fatal error

Posted: September 18, 2012 at 4:49 pm

Viewing 7 reply threads


Eric Martin

September 18, 2012 at 4:49 pm

I’m trying to upgrade to 3.1.27 and when I try to activate it I get

Warning: require_once(/homepages/38/d377799762/htdocs/website/wp-content/plugins/event-espresso/class/espresso_log.php) [function.require-once]: failed to open stream: No such file or directory in /homepages/38/d377799762/htdocs/website/wp-content/plugins/event-espresso/espresso.php on line 176

Fatal error: require_once() [function.require]: Failed opening required ‘/homepages/38/d377799762/htdocs/website/wp-content/plugins/event-espresso/class/espresso_log.php’ (include_path=’.:/usr/lib/php5′) in /homepages/38/d377799762/htdocs/website/wp-content/plugins/event-espresso/espresso.php on line 176

Any thoughts?


Chris

September 18, 2012 at 4:57 pm

About 3.1.27
On the individual events page the php for price is gone and price doesn’t show up.

Start Time: 5:00 pm
End Time: 7:00 pm
Price: $35.00

So that’s different.

Reverted to my 3.1.26 backup for now.


bhannon

September 18, 2012 at 5:50 pm

I too get fatal errors in trying to activate 3.1.27 with errors in the same line 176:

Warning: require_once(/home4/sixteen2/public_html/wp-content/plugins/event-espresso/class/espresso_log.php) [function.require-once]: failed to open stream: No such file or directory in /home4/sixteen2/public_html/wp-content/plugins/event-espresso/espresso.php on line 176

Fatal error: require_once() [function.require]: Failed opening required ‘/home4/sixteen2/public_html/wp-content/plugins/event-espresso/class/espresso_log.php’ (include_path=’.:/usr/lib64/php:/usr/lib/php:/usr/share/pear’) in /home4/sixteen2/public_html/wp-content/plugins/event-espresso/espresso.php on line 176

  • This reply was modified 12 years, 4 months ago by bhannon.


svincent

September 18, 2012 at 7:17 pm

Same here, could really use some advice here as my entire site is down because of it.


Seth Shoultes

  • Support Staff

    •

September 18, 2012 at 7:22 pm

Sorry for the trouble! Please re-download and install the files.

One of the files didn’t get exported from the svn correctly or was corrupted. I just exported everything again, ran a test install, and it installed fine this time.


Seth Shoultes

  • Support Staff

    •

September 18, 2012 at 8:03 pm

@Chris we modified the event_registration_display.php file so that it uses an action to display the price, instead of the big block of code that was there before. So you will need to update your template files.

That block of code wasn’t very well optimized, and was hard to update, so we replaced with the new action.


svincent

September 18, 2012 at 8:44 pm

Worked great Seth! Thanks!


bhannon

September 18, 2012 at 9:02 pm

Thanks, Seth! That worked for me!
Viewing 7 reply threads

The support post ‘Upgrade to 3.1.27 triggers fatal error’ 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 bhannon 12 years, 4 months ago ago

Topic Tags

Notifications

This topic is: resolved
Event Espresso - Staging Server