Evo site: Provisioner or wait for MODX 3?

So, having read your comment, am wondering just what the difference is between Evo (1.0.8 or any of the later versions) and ClipperCMS?

It's a shame Evo's falling by the wayside, in any case. Evo and Revo are two difference animals, for two different client types.

Clipper is a fork of Evo, somewhere around 1.0.6. The only modification to Evo since then is a security patch. I don't know how much Clipper has been modified since the fork.

http://www.clippercms.com/forum/new-features-new-release-summaries/clipper-1-1-rc/msg374/#msg374

ClipperCMS is a fork of Evolution so it shares the same common base at this point in time. Going forward there will be differences, but I am unaware of any major differences at this point in time.

From what I can tell the biggest difference is that ClipperCMS has addressed the issue of PHP 5.4 as well as fixing some of the outstanding bugs.

Quote from: exside at Feb 20, 2013, 10:44 AM

Quote from: sitecms at Feb 20, 2013, 08: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!

Take a look at this project: http://processwire.com/

We're been in love with MODX since 2008 and also thought that nothing would come between us - untill couple of weeks ago. PW has so powerful API, simple and logical filesystem plus great built in features that makes MODX to look bit messy and outdated compared to PW.

http://www.mademyday.de/why-i-chose-processwire-over-modx.html

I've read a bit about PW; it strikes me as having some mysterious areas. I'm more of a designer than a techie (altho I felt at home with Evo). PW intrigues me, but lurking in the background is the fatigue that there is a whole new system to familiarize myself with! Still, many enthusiastic reviews; will examine further.

Thanks for your thoughts!

Yes, after evo, not revo but processwire is for the rest of us (designers)

I'm a designer too and even when I don't like extJS, the Revo API is just so nice...it takes some digging to wrap your head around and yes, sometimes it's frustrating...just had a look at processwire, nothing against the API, also looks good, and the possibilities are good for sure, but when I saw the "manager" / Admin Interface I just have to say...nooo way =D, as a designer I like aestethicly appealing interfaces, and for me this is definitely not true for PW...I don't know if there are PW-Skins for the manager or so, but if not it would make me sad to look at all that unstyled forms all day =))

I did see one video demo of somebody's manager theme; it looked a lot nicer. I wasn't real happy with their template system - HTML code with inline PHP. Simple, but not so good for client editors.

when you, as a 'backend'-developer, work together with 'frontend' - developers and designers, its a must to have separated logical- and the layout-stuff.
This is one of the great advantages of MODX with its templates/chunks/placeholders and its parsing-system.
processwire seems to have only plain php - templates, which for sure is simple and may make things fast, but can make it very frustrating, when your frontend - developers have to bother with php-tags in between their html tags and may ruin your development-work.
It would never came to my mind to change Revo (or Evo) with something like processwire for bigger projects, and when working together with more than one people on it at the same time, so far I can tell about it. (had just the time for a quick lookup into it, some time ago)