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
ee4 disaster! How do I revert back to the old version? | Event Espresso - Staging Server

Support

Home Forums Event Espresso Premium ee4 disaster! How do I revert back to the old version?

ee4 disaster! How do I revert back to the old version?

Posted: March 4, 2014 at 5:21 pm

Viewing 3 reply threads


rachel Perry

March 4, 2014 at 5:21 pm

ee4 disaster! How do I revert back to the old version?


Josh

March 4, 2014 at 5:40 pm

Hi Rachel,

You can revert to the old version by deactivating Event Espresso 4, then:

option a) restore the database to the backup you made before installing Event Espresso 4

or

option b) re-activate Event Espresso 3 and set up the shortcodes and registration/checkout pages as outlined in this guide:

http://staging.eventespresso.com/wiki/the-basic-settings/#page


rachel Perry

March 4, 2014 at 5:46 pm

I apologize, I’m not a programmer and this is all SO confusing to me.

I installed the custom template add-on. How do you I this? Also, how do I customize the single event listing page? I can’t seem to find this. I appreciate your help.


Sidney Harrell

  • Support Staff

March 4, 2014 at 9:14 pm

Have you successfully reverted back to EE3, and are trying to use the custom template add-on with it? Or are you trying to use the custom template add-on with EE4? None of the current add-ons are compatible with EE4.

Viewing 3 reply threads

The support post ‘ee4 disaster! How do I revert back to the old version?’ 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