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
3.1.30P upgrade failed | Event Espresso - Staging Server

Support

Home Forums Event Espresso Premium 3.1.30P upgrade failed

3.1.30P upgrade failed

Posted: January 31, 2013 at 8:23 am

Viewing 3 reply threads


Suhaib Siddiqi

January 31, 2013 at 8:23 am

Automatic update to v3.1.30P failed with the error message “Update failed due to missing /evente-spresso/espresso.php. Although espresso.php was there. I had to ftp, delete 3.1.29P and manually upload the new version.
Well… it update 3.1.30P is a mess. Now my Event View page shows only [ESPRESSO_EVENTS]. Here is the link http://www.shaadiconnections.com. I am reverting to version 3.1.29P because we have an event in a two weeks, and people are buying tickets everyday.
After reverting to 3.1.29, I tried again the upgrade same issue upgrade fails. I noticed the eventespresso.tmp directory in my wp-content/plugin. The event-espresso was gone. Apparently upgrade is failing half way through.


Peter

January 31, 2013 at 8:39 am

I had the same problem. Go to Plugins>inactive and reactivate the EE plugin.


Suhaib Siddiqi

January 31, 2013 at 8:55 am

I tried that too, before reporting the issue.


Josh

January 31, 2013 at 10:08 am

Hi Suhaib,

Thanks for reporting. There was a problem with the zip file and we’ve uploaded a fresh copy of the file that resolved the issue. I’d recommend trying that again.

Viewing 3 reply threads

The support post ‘3.1.30P upgrade failed’ 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