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
Fatal error - Website down after upgrading to EE4 | Event Espresso - Staging Server

Support

Home Forums Event Espresso Premium Fatal error – Website down after upgrading to EE4

Fatal error – Website down after upgrading to EE4

Posted: March 1, 2014 at 12:38 am

Viewing 2 reply threads


Steven Phillips

March 1, 2014 at 12:38 am

Hi,

I had a website operating the latest version of EE3 at http://www.watersidemetalart.org and after trying to upload EE4 the site has gone down. When I try to enter it gives the following message:

Fatal error: Cannot redeclare espresso_version() (previously declared in /home/content/38/9739238/html/wp-content/plugins/event-espresso-core-reg/espresso.php:31) in /home/content/38/9739238/html/wp-content/plugins/event-espresso/espresso.php on line 35


Josh

March 1, 2014 at 8:19 am

Hi Steven,

You will need to deactivate Event Espresso 3 before you activate Event Espresso 4. You’ll likely need to manually deactivate Event Espresso by re-naming the either of the Event Espresso plugin’s folder using your host’s control panel or with FTP. Here’s a guide that outlines a few options on how to disable a plugin without access to the WP admin:

http://www.ostraining.com/blog/wordpress/disable-a-wordpress-plugin/


Steven Phillips

March 1, 2014 at 11:43 pm

Thanks Josh, we have resolved this now

Viewing 2 reply threads

The support post ‘Fatal error – Website down after upgrading to EE4’ 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