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 developers pack-Can I downgrade 2 sites to EE3| is EE4 multisite compatible? | Event Espresso - Staging Server
Hello, I am considering purchasing the EE4 developers package, as I have two sites and maybe another where I will use EE.
On two of the sites there are potentially going to be issues with the EE4 and I might need to revert to EE3.
My question is would it be possible to keep ee4 on a few sites and change down to ee3 if I needed to?
Also, one of the sites is using a multisite installation of wordpress and would this be a problem?
Also, if you happen to have a vague idea – when would mailchimp integration approx be available?
Cheers, Sam
Event Espresso 4 will prompt you to migrate data from Event Espresso 3 but you cannot easily migrate from version 4 back to version 3. Any new registrations would need to be manually added when moving back to version 3.
Also, you can’t run both versions at the same time.
The MailChimp addon for EE4 is currently being developed. It will then go through a testing phase before it is released.
—
Lorenzo
Viewing 1 reply thread
The support post ‘EE4 developers pack-Can I downgrade 2 sites to EE3| is EE4 multisite compatible?’ 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.
Post any questions about the language files, translating Event Espresso, or issues with our GlotPress site for translations here.