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
White Page of Death after Wordpress 3.6 upgrade | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › White Page of Death after WordPress 3.6 upgrade

White Page of Death after WordPress 3.6 upgrade

Posted: October 18, 2013 at 3:00 pm

Viewing 4 reply threads


cpurcell

October 18, 2013 at 3:00 pm

After upgrading wordpress I got the white page of death. I’ve deactivated every other plugin, I’ve changed themes, tried default themes with no plugins, tried my theme with no plugins…you name it. Anytime I activate Event Espresso, I get the ever-popular WordPress White Page of Death. I’m very frustrated and annoyed. Please help!


Josh

October 18, 2013 at 3:27 pm

Please see this guide on how to trouble shoot this:

http://staging.eventespresso.com/wiki/troubleshooting-event-espresso/#wsod


cpurcell

October 18, 2013 at 3:52 pm

I tried all that. Still having the issue. My usage for mem was at 40M, so I bumped it to 64 as in the post. Still can’t activate Espresso.


Josh

October 18, 2013 at 3:57 pm

I set up a log file on your server and this is the fatal error that is being thrown when Event Espresso is activated:

PHP Fatal error: Class ‘Event_Espresso_Widget’ not found in /xx/wp-includes/widgets.php on line 324

So it could be something missing in your WP installation -or- the Event Espresso plugin wasn’t installed correctly. I’ll try uploading a fresh copy of Event Espresso first.


Josh

October 18, 2013 at 4:15 pm

I found the cause of the issue: a blank widget.php file in /wp-content/uploads/espresso/templates.

What was happening was WordPress was trying to load up its widget class and the blank file there was overriding the widget.php in Event Espresso core. I’ve renamed the /wp-content/uploads/espresso/templates directory to /templates-old so that Event Espresso can load up its widget.php template.

I’ll delete the log file now that this has been sorted out.
Viewing 4 reply threads

The support post ‘White Page of Death after WordPress 3.6 upgrade’ 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 Josh 11 years, 3 months ago ago

Topic Tags

Notifications

This topic is: not resolved
Event Espresso - Staging Server