I have a non-profit on 2.4.0 that is on a paid full version when that was the best deal for non-profits.
At this point I’d like to upgrade them to the new release and the free core version.
What must I consider in order to do this? We’re not using anything fancy in 2.4.0 (e.g. forums). That said, I did notice a red X in the Members row of core. What does that mean?
Thanks in advance.
Thanks Jim.
But mine is not a question about price, but a technical one.
We’d be going from the paid full 2.4 to the “core” 2.6.
1) Is that possible? (Yes, I know, in theory everything is possible 😉 )
2) What are the possible bumps in the road that we’d need to aware of prior? For example, if you’re using X, Y and Z (EE stuff, as well as 3rd party add-ons) in 2.4 that might be a problem in 2.6.
Yes, in versions 2.4 to 2.6 is an “upgrade”. However, it also means down shifting (?) to just EE core.
Thanks again.
I guess the question I have is why do you want to move to core when you can just upgrade to full version for no cost? Why bother wading into murky ground when the path from 2.4 -> 2.6.1 is well worn?
As to a real answer to your question, you’ll have to research which addons you are using in 2.4 that don’t run in core. I doubt that you’ll find a supported upgrade path, or a core installer that’ll upgrade 2.4 full install. You could just do a new 2.6.1 core install and migrate old data to the new install.
But still, why do you want to go to all this trouble?
I see this thread is a little stale, but FWIW, I was in a similar situation as the original poster in that I wanted to migrate a site from an older full version (2.3.1) to the current core version (2.6.1).
What wildrock says makes total sense, and yet I still wanted to do the migration for my client for a couple reasons: I didn’t want them to run into this issue down the road when EllisLab comes out with EE 3.x, and I wanted to make sure to minimize any potential confusion about which version they have and what features they are entitled to for the budget they have.
I did some spot comparisons between the current full version and core files. It seemed that differences were isolated to language and modules, which made sense to me. I then just followed EE 2 update instructions, using the core files instead of the full version, and it worked without any glitches.
Note that the site that I was migrating from the full version to core did not rely on any modules that are excluded from core. It also wasn’t utilizing any add-ons that are not supported for core.
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.