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
Lost all customizations after updating to EE version 3.1.35.1 P | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Lost all customizations after updating to EE version 3.1.35.1 P

Lost all customizations after updating to EE version 3.1.35.1 P

Posted: October 8, 2013 at 4:01 am

Viewing 3 reply threads


Jake Vizner

October 8, 2013 at 4:01 am

Just wanted to let you know that I lost all my files located in /wp-content/uploads/espresso/ folder. After the upgrade the folder was empty, I had to re-upload the js files and custom_fucntions.php file back to the server.

Thank you,

Jake


Dean

  • Support Staff

    •

October 8, 2013 at 4:12 am

Hi Jake,

Thanks for the information, I will look into this. Can you advise the version you upgraded from please?


Jake Vizner

October 8, 2013 at 4:33 am

I upgraded from the version 3.1.35 P

Jake


Dean

  • Support Staff

    •

October 8, 2013 at 4:46 am

Hi,

Thanks for the confirmation.

We haven’t received any other comments regarding this and my tests have not confirmed the upgrade is responsible. Plus the upgrade code should not touch the uploads folder at all.

Could there be another issue more local to your own server?
Viewing 3 reply threads

The support post ‘Lost all customizations after updating to EE version 3.1.35.1 P’ 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 Dean 11 years, 5 months ago ago

Topic Tags

Notifications

This topic is: resolved
Event Espresso - Staging Server