Posted: 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? |
|
About 3.1.27 Start Time: 5:00 pm So that’s different. Reverted to my 3.1.26 backup for now. |
|
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
|
|
Same here, could really use some advice here as my entire site is down because of it. |
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. |
|
@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. |
|
|
Worked great Seth! Thanks! |
|
Thanks, Seth! That worked for me! |
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.