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
Rolling Back to 3.1.27 | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Rolling Back to 3.1.27

Rolling Back to 3.1.27

Posted: October 26, 2012 at 10:06 am

Viewing 4 reply threads


Eamon Duede

October 26, 2012 at 10:06 am

I upgraded to 3.1.28 and am having the problems. How exactly to I roll back? I downloaded the older version and tried to install it up the install failed. I want to roll back but don’t want to lose any data.


Josh

October 26, 2012 at 10:53 am

Hi Eamon,

I’m sorry for the trouble. You can avoid losing data by backing up the database before switching versions.

It’s likely the install failed because the other version of Event Espresso was still on the server. You can remove the existing version from the server before uploading 3.1.27. We’re working on fixing 3.1.28 and will be rolling the hotfix release as soon as we can.


Eamon Duede

November 1, 2012 at 9:12 am

Alrighty, I can’t wait for the hotfix any longer. Where is the database located on the server relative to wp-content?

also, what do you mean by “remove from the server”? Do you mean “Deactivate plugin” or do you mean going into the ftp client and deleting the “/espresso” directory?

After I’ve “removed it from the server” and then installed the 3.1.27 version and activated it, do I then just upload the database to where I backed it up from? Is that all?

-Eamon


Josh

November 1, 2012 at 9:22 am

Hi Eamon,

The database isn’t relative to wp-content. You can backup your database by logging into the host control panel, and most control panels have an interface named phpmyadmin.

A simpler alternative would be to use a plugin to back up all the database tables. The one I use is wp db backup:
http://wordpress.org/extend/plugins/wp-db-backup/

Removing from the server means deleting the plugin. You can do this from wp-admin/plugins.php. Step 1 is deactivate the plugin. Step 2 Once it’s deactivated, a delete link will appear (it will be colored red).

Step 3 is install and activate the other version of Event Espresso.

You will not need to upload the database, because you’re only removing files and replacing them. When you activate Event Espresso, it will update the database automatically. Backing up the database is a pre-cautionary step.


Eamon Duede

November 1, 2012 at 9:27 am

Thanks, Josh!
Viewing 4 reply threads

The support post ‘Rolling Back to 3.1.27’ 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 Eamon Duede 12 years, 2 months ago ago

Topic Tags

Notifications

This topic is: resolved
Event Espresso - Staging Server