Evo site: Provisioner or wait for MODX 3?

I have a site that is running on MODX 1.0.6 (am upgrading it to 1.0.8 tonight). Is it worth abandoning and moving to Revo, or ok to wait for MODX 3?

It's doing what it needs to do for the client, but am interested in opinions.

Thanks!

Personally I would transfer it to Revo now if you have the time as a revo to MODX 3 upgrade will come before a evo to MODX 3 upgrade, it will also give you a little more time to get used to revo and it's a lot more stable / powerful.

My personal opinion: wait for MODX 3

I see no point at this time in converting an EVO site to REVO, and then to MODX 3

Not only that, there is a large learning curve from EVO to REVO - so if code does change again between REVO & MODX 3 you will have to learn it all again - good, I dont know if that will be the case but at the moment you never know.

EVO & REVO are on their way out, as has been published by the MODX team.

MODX 3 is supposedly being released sometime this year, so until then, if your site is still working OK. leave it.

Before upgrading to 1.0.8 I suggest reading the changes, as not much has been changed 1.0.7 => 1.0.8 was just a security fix on Forgot Manager Login, in actual fact the changes from 1.0.6 => 1.0.8 are only to do with Forgot Manager Login, as can be seen here

Cheers

p.s If you do go ahead with migrating the site, you might want to look at this first

Thanks very much for your responses and opinions. I'm leaning toward not converting this site, because they are used to it and it serves their purposes sufficiently. I disabled the Forgot Mgr plugin a while back, so that's not a concern. I think I will wait. Maybe ClipperCMS will be sailing by then, right?!

The question now is whether it's worth updating to 1.0.7, even?

If it's not broken, why fix it? If Evolution offers all the functions your client needs I wouldn't upgrade to Revolution unless your client is willing to pay for the work. It's not a simple upgrade if you are using the typical Evolution snippets (Ditto, eForm, Jot...). Especially Jot comments are pain since there is no export/import tool for Jot => Quip. [ed. note: Lammikko last edited this post 13 years, 7 months ago.]

I see no point at this time in converting an EVO site to REVO, and then to MODX 3. Not only that, there is a large learning curve from EVO to REVO - so if code does change again between REVO & MODX 3 you will have to learn it all again

=> Plus the time for helping your editing clients 2 times to adapt to the changes and explaining 2 times why. Plus for me going to learn extJS, but the modx manager doesn't work on an iPad ? Or wait for modx3 ? I like modx, but for all this as said before, I simply don't have the time. Especially not in these days where everything is being pushed faster and faster. I'm spending my time now evaluating around 20 cms'es to come up with a cms that is procedural in the core, speed also without cache, scalable, maintainable by myself for php 5.x, jqueryUI backend, indexed database tables, templates and fields with a likewise api. It's going to take me a month I think but it will be time well spend.

Quote from: sitecms at Feb 20, 2013, 02:11 AM

I see no point at this time in converting an EVO site to REVO, and then to MODX 3. Not only that, there is a large learning curve from EVO to REVO - so if code does change again between REVO & MODX 3 you will have to learn it all again

=> Plus the time for helping your editing clients 2 times to adapt to the changes and explaining 2 times why. Plus for me going to learn extJS, but the modx manager doesn't work on an iPad ? Or wait for modx3 ? I like modx, but for all this as said before, I simply don't have the time. Especially not in these days where everything is being pushed faster and faster. I'm spending my time now evaluating around 20 cms'es to come up with a cms that is procedural in the core, speed also without cache, scalable, maintainable by myself for php 5.x, jqueryUI backend, indexed database tables, templates and fields with a likewise api. It's going to take me a month I think but it will be time well spend.

It would be interesting to me if you find something that fits your needs better than MODx =), could you post back your findings/evaluation results? Thanks in advance!

Quote from: ridgeofdemolition at Feb 19, 2013, 06:14 PM

The question now is whether it's worth updating to 1.0.7, even?

Personally if you have already fixed the security issue there is no benefit in updating to 1.0.7 or 1.0.8 for that matter.

If you decide you don't want to continue to use a CMS which isn't being developed then evaluate all the alternative CMSs, like sitecms is doing, as there might be one that better suits your project than Revo. Especially check their longevity, if possible, as it's a mistake I made when switching to Evo. Hopefully ClipperCMS will extend the life of Evo for a couple more years yet.

Yes, I agree; continuing with 1.0.6. Everyone's happy, so why mess with it? Revo is too much for this situation. Will keep an eye on ClipperCMS.

I'd welcome suggestions of any other Evo-like cmses, as well. Research is not always the same as current use.

Thanks!

I'm also trying to replace php 5.4 deprecated stuff inside Evo 108. I won't give up on Evo so easy