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 Questions about Upgrading to EE4 | Event Espresso - Staging Server
Hello.
I have a couple of questions about upgrading to EE4.
1. I read that EE3 will merge into EE4. Does that mean all events, data, questions, etc will carry over? Is there anything that will not carry over? What might I risk losing? What steps do I need to take to do this?
2. If there are problems, can I downgrade back to EE3 and still keep my data?
You should always make a backup of your site before upgrading so if something unexpected happens then you can revert back to EE3. However, you can upgrade to EE4 and then revert to EE3 and the only issue will be changing your EE3 shortcodes back to how they were before the upgrade (check your critical pages, calendar shortcodes, etc.). Your registrations, transactions, questions, answers, etc. should carry over just fine.
EE4 will try to accommodate most data that you have in EE3 but it will not be accessible without add-ons. The interface has changed so we haven’t accounted for displaying that data in EE4 (yet).
Have you tried out EE4 on a blank/new WordPress installation just so you’re familiar with how it works?
Does this help?
Viewing 1 reply thread
The support post ‘Questions about 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.