Posted: September 23, 2014 at 2:13 pm
|
|
We currently use Event Espresso Version 300.1.35.2.P an a multi-site WP instance and are considering upgrading to EE 4.4 or the most recent version of EE 3.X We also purchased the following addons which we will need to update to the most stable version: Event Espresso – Calendar – Version 200.0.6.3 NOTES: – General Settings QUESTIONS: – We have had read mixed reviews regarding using EE 4X on a multi-site instance. Can you provide us your stance/thoughts. – What plugins listed above that we use currently will have issues with the current stable version of EE 3.x or EE4.4 – Where on your site can we learn about the benefits to making the upgrades outside of your change log? – Assuming that we will have to reconfigure the entire EE with an upgrade, what data can we save off (either by cut and paste of text, or restore from a DB) to keep the downtime at a minimum? Is this feasible? Do you have any tools / strategies we could follow to accomplish this? – What is our exposure if we maintain the current version of EE? Lack of stability? May not work with future versions of WP or new EE plugins? |
|
Hello Cliff, We do not officially support multi-site installations as they present different challenges than a single site install. Based on your add-ons and custom coding, we recommend updating to the current version of Event Espresso 3.
Event Espresso 3 information will be migrated to Event Espresso 4. Custom email templates are not migrated as those have been replaced with a new messages system.
Again, we do not officially support multi-site with Event Espresso 4. This may change in the future after we have had more time to test Event Espresso 4 on various multi-site environments.
The calendar is available for Event Espresso 4. The other add-ons and the calendar are available for the current version of Event Espresso 3.
See these pages: https://eventespresso.com/differences-ee4-ee3/ They will be updated soon as we release additional add-ons for Event Espresso 4. A promotions system is also under development and will be available as an add-on next year.
Your custom emails templates will need to be saved. Other than that, your information should migrate without any issues. Note: you’ll need to first update to the current version of Event Espresso. Also, the migration will not work if you have modified how Event Espresso stores information in the database.
We recommend updating to Event Espresso 3 as we support that version https://eventespresso.com/wiki/change-log/ What kind of custom coding is in use on your site? — |
|
|
|
Hi Lorenzo, ALL questions below pertain to a multi site instance. 2. If the answer to the above question is yes we have to remove and re install vs. update how do we backup the data in the existing system and restore it back without redoing it all manually? Any tips/guides/strategies or suggestions would be very helpful 3. Based on past support and experience what challenges do you anticipate us having if we upgrade Event Espresso Version 300.1.35.2.P most stable version of EE 3.X in a multi site environment. 4. Are there known issues for this plugins in an multi site environment if we upgrade to most stable 3X versions of these? Thanks for your time and assistance with this. |
|
|
Hi, 1) EE3 can be installed on multisite, but has to be installed on each individual site. As such your licence is only good for one of those sites (we treat each site on a multisite as a separate entity). To upgrade the others you would need to manually delete and re-upload the latest version. Please also note that support will only be given for the site with the valid licence. 2) Removing the plugin will not remove the data from the database. If you are concerned, you can of course use a backup plugin to take copy of the database, prior to updating the plugin. 3) Upgrading from 3.1.35.2 to the latest version in itself will pose no challenges. Adding it to a multisite might incur some issues. As stated above, it cannot be network activated. As such every site with the plugin on it will be separate, including the databases, so will be unable to share data. You could instead use the JSON API addon, install the plugin on one site and pull event data across (you will likely need a developers assistance with this as the JSON API is not really for general use as it will require coding to make use of). 4) None that we are aware of as long as they are activated on a single site basis (not network activated). The short answer for all of this is that if you want a single installation of the plugin to function on many sites then it wont work. Instead you would have to treat each site as an individual site and install the plugin individually on each. Depending on the number of sites you have/have planned then this could quickly become a logistical problem, especially on updates. |
|
|
Hi there, Although we are running a multi-site project we only have it installed & configured on a single site. We do not actually need it on others at this point. So that being said can you frame your responses to these questions: ALL questions below pertain to a multi site instance. Event Espresso – Calendar – Version 200.0.6.3 Sorry I am just trying to get a response that covers all bases and appreciate the help! |
|
Hi Cliff, I’ll follow up with each of your questions below:
For you, since you are on multisite, you’ll follow the manual update guide: https://eventespresso.com/wiki/updating-event-espresso/#update_manually
I do not anticipate issues unless you’ve made modifications, which seems to be the case since you mentioned this:
That’s the challenge you’ll face if you’ve modified core files. A good tool to help with migrating changes from one version to the next that I can recommend is diffMerge. Along with that I can also advise, where possible, to keep modifications outside of core EE files. This way you will not lose the modifications on an update. While you’ll still need to maintain your modifications, keeping modifications in separate files makes for less work when they are in separate files outside core. Modifications can be done via actions hooks, filter hooks, pluggable functions, and if they are text string changes they can be done via a translation function. Event Espresso 3 also has an override-able template system, and you can read more about how it works here: https://eventespresso.com/wiki/put-custom-templates/ If you require detailed assistance with migrating customizations from one version to another, we recommend contracting with one of the developers listed on this page: https://eventespresso.com/developers/event-espresso-pros/ A little additional clarification, you’ll be updating from Event Espresso 3.1.35.2.p to 3.1.36.6.p. The differences between the two are mostly bugfixes and a few enhancements. You can review the differences in our changelog, starting here, then scroll up.
The known issues will potentially happen if you do not upgrade to the most recent add-ons when updating to the newest version of Event Espresso 3. Please be sure to update to the 2.2.4.p version of the Event calendar. The others you list here are up-to-date version numbers. |
|
The support post ‘Technical Configuration Request’ 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.
