|
Eric Amundson
|
June 4, 2015 at 12:50 pm
Hi Team!
I have a client running EE4 on a multisite installation where EE4 is only used on one of the multisite instances. It’s installed at the network level and activated on this one site.
Multisite isn’t supported by EE4, correct? But you can still set it up so that at least one of the sites gets automatic updates?
Please let me know if I’m wrong. But ideally, I’d want to know the process for:
a) where to install the license key for auto updates (on the network level or site level?)
b) if on the site level, where do I put in the license key? (the normal key field isn’t showing on the Event Espresso General Settings page)
c) if it’s on the network level (again, I can’t find where to add the license key), would updating EE on the network automatically update the versions on the individual sites?
Thank you. 🙂
-Laura
|
|
Lorenzo Orlando Caum
|
June 4, 2015 at 1:33 pm
Hi Laura,
Automatic updates would only be available on the primary site because the primary site would have a support license key field.
If you are not on the primary site and are using a subsite, then automatic upgrades would not be available and you would need to manually update.
—
Lorenzo
|
|
Eric Amundson
|
June 4, 2015 at 4:11 pm
Thanks, Lorenzo. So, in the case of multisite, it isn’t clear to me where to enter the license key as the primary site (which would be the network root of the multisite) doesn’t have a place to add the license key. Is there a better way to set the license key?
|
|
Darren Ethier
|
June 4, 2015 at 4:54 pm
Hi Laura,
Just thought I’d chime in here to bring clarity to how the license key works with multisite. Currently we do not support fully automatic updates of EE on multisite officially. However, the way it is setup is that in order to get automatic updates, you must have EE network activated. Then the license key field will appear on the main site for the primary network (if this is not only a multisite but multi-network install). Automatic updates will then be possible from the main network admin.
However, and this is important, we currently have open tickets for issues with the site-license key disappearing after an update on multisite. It’s resolved by just reentering the key.
So, the tldr; is that there is no way to do automatic updates in the current setup you have, and the plugin will have to be updated manually. At some point in the future we may invest in better automatic update support for EE4 when in a multisite environment but its not a priority right now (and we’ve found that many WordPress multisite users update using some sort of version control system anyways).
Aside from this limitation, EE4 should work really well in a multi-site environment (we use it on EventSmart! 🙂 )
|
|
Eric Amundson
|
June 4, 2015 at 5:15 pm
Hi Darren!
Thanks so much for the clarification! 🙂 So in short, I can do auto updates, but every time I do them, I should double check the key on the network level and (if it’s missing) re-add it in.
That helps clear up some things with this client we’re working with. (And it also has me better informed for multi-site instances with other clients that may use EE4). 🙂 So thanks so much for educating me!
-Laura
|
