|
TODD
|
May 8, 2014 at 4:18 pm
Can you give me an idea of when you foresee Multi-site support for EE4?
It’s rather critical for me.
Thanks,
-Todd
|
|
Lorenzo Orlando Caum
|
May 8, 2014 at 5:31 pm
Hello,
We don’t officially support multisite installations but we do know that a handful of members are using EE4 with multisite.
What kind of support are you looking for?
—
Lorenzo
|
|
Dean
|
May 9, 2014 at 1:44 am
Hi,
I think the question should be “Will EE ever support network activation?”. The answer to that is: not in the foreseeable future.
EE3 or 4 should both work fine on single site activations, as for all intents and purposes these are individual sites.
|
|
TODD
|
May 9, 2014 at 6:00 pm
I have EE3 running on a multi-site and it is working fine with three subsites, three individual licenses.
The main issue that requires a multi-site is multiple locations for payment processing. Secondarily is data segmentation but primarily the payment gateways for each location are different.
If EE4 will specifically not function on multi-site and if that is the intention and direction then it will be unfortunate but EE4 will not be a choice as an upgrade.
|
|
Garth
|
May 13, 2014 at 2:37 pm
Hi TODD,
EE4 does technically work by being network activated. That’s how we’re running http://demoee.org.
We have not fully tested migrations from major versions, but 4.1 to 4.2 seemed to go fine. Each blog is required to run the migration scripts when necessary.
We have not tested EE4 multisite on a per-site activation.
Overall, we are keeping multisite compatibility in mind as development progresses, but we don’t officially support multisite just because it hasn’t been fully tested nor have we worked out pricing for larger multisite installations.
Does that help?
|
|
TODD
|
May 14, 2014 at 12:04 pm
Thanks for the update Garth.
The way I’m handling my multisite with version 3 (v. 3.1.36.5.P) is:
— EE is not “network activated” on the multisite, and
— Each subsite that requires EE is activated and has it’s own license applied.
…this works. There are a few issues which require the multisite to be separate instances: the primary issue is: each site has it’s own payment gateway, and secondarily we can manage users more granularly.
— I have three sites running within the multi-site but I was planning on paying for each license above 5 when it came to that. I would happily welcome a different pricing structure especially if it was less $$! 🙂
If this next question should be a separate topic, let me know but:
— Are you planning any support for migrating the actual data from 3.1.36 up to v.4.x? (or have you already tested this?)
— I got a lot of errors on a very basic upgrade test but did not look at the result (that’s not helpful but it’s the truth!). Since I got so many errors, I just moved on to something that was more pressing.
I think that’s it for now.
-T
|
|
Garth
|
May 14, 2014 at 3:36 pm
Todd,
We can arrange discounted pricing for more licenses than are currently included with the Developer License. We do have customers with dozens of license keys but that is a manually agreed upon and adjusted process.
We do have data migration support for 3.1.36+, but only for single site licenses. We have never tried to migrating a multisite installation of 3.1.36 to a multisite installation of EE4.
|
|
Josh
|
May 14, 2014 at 3:39 pm
Along with that, each site can have its own payment gateway settings when Event Espresso is network enabled.
|
