MODX Evolution return! (version 1.0.9 from 03/19/2013)

Recently, an active movement has been marked in the MODX development camp, which has already resulted in the organization of a global network of Ambassadors, the appearance of a long-awaited cloud for the Revolution branch and, most importantly, the official revival of the Evolution branch, the development of which the creators have long abandoned. So, on March 19, 2013, the followers of the branch did not cease to hope.
Evolution for the last two years and what confirmed the honorary title of MODX, as the most promising and fast-growing open source control system in 2012 ( subject ).

In general, the idea itself had been hatched for a long time, the system continued its development, independent of the official developers, in informal assemblies, but there was a desire to change the situation for the better. And a few months ago, just after the launch of the MODX Ambassador program, I raised this topic in an interview with one of the creators of MODX - Ryan Thrash. Taking into account the fact that MODX 3 is only in the plans (and very remote), and the MODX Revolution branch was not impressed by many, the topic of continuing development of the MODX Evolution branch was of great interest to almost the entire founding team.

The result of the negotiations was the offer made to me to join the MODX team as a developer of the Evolution branch, which I could not ignore. Another member of the MODX Russian-speaking community, Agel_Nash , a well-known Japanese developer, author of MODX.jp , Mansor Yamamato (yama) and German Thomas Jakobi (jako), the developer of MultiTv and other solutions for the Evolution branch, also got into this team. The symbiosis turned out quite successful and, thanks to the well-coordinated and hard work, we managed to release MODX Evolution 1.0.9.
')
The main problem that the new release solves is compatibility with php 5.4, which is important in the light of the upcoming April transfer of some hosters to version 5.4 and disabling all earlier versions. Also, in addition to fixing old bugs, new features were added, which many people lacked. In detail, all this can be seen in the changelog , I personally want to highlight such "buns" as:

Significant processing parser:

[[SnippetA? &param1=`value` //   &param2=value &param3='value' &param4="value" //         `` &param5=`[[SnippetB]]` //        &param6=`A&B=C?` //     ]] 

The appearance of backup manager:


Added Snippet IF ( wiki ) :
Snippet to display information on the condition.
Operation logic: If the is condition is satisfied, then we output the contents of the then parameter; if not, then we output the contents of the else parameter.

 [[if? &is=`[*id*]:=:4:or:[*parent*]:in:5,6,5,7,8,9` &then=`[[if&is=`0||=||0` &then=`true` &else=`false` &separator=`||`]]` &else=`@TPL:else`]] [[if? &is=`[*id*]:is:1:or:[*id*]:is:2:and:[*parent*]:is:5:or:[*parent*]:in:2,3,4` &then=`true` &else=`false`]] //     (....:or:is:.... ) :and: (...:!empty:.....) // and    2 ,        true //: // (is,=) , (not,!=) , (>,gt) , (<,lt) , (>=,gte) , (lte,<=) , (isempty,empty) , (not_empty,!empty) // (null, is_null) , (in_array, inarray, in) , (not_in,!in) //         >300$ <=700$ [[if? &is=`[*price*]:>:300:and:[*price*]:<=:700` &then=`@TPL:akcia`]] //     3 [[if?is=`[+ditto_iteration+]:%:3` &then=`true` &else=`false`]] 

Separately, I would like to mention the main development team to which we have joined. They showed themselves from a very good side, paying attention to our proposals, many of which were embodied in the release or are already planned for the next.

But the development of the unofficial Russian assembly MODX Evolution will also be continued, as it includes many third-party add-ons that make life easier for the developer. I once wrote a post about her, but it’s clear that the stars were such that he didn’t go beyond the sandbox, so I suspect that many who he might find useful have simply not seen him. It does not make sense to copy it all, but in short I will tell you a little about it.

Initially, the idea to create some kind of assembly was not. There was a desire to save time on installing the site and those add-ons that were very often needed. But, as often happens, then I wanted to add something else, it took something to change, the assembly itself settled on GitHub and in less than two years of its existence it grew into a flexible, fast and functional product. Today, it has more than 500 sites (these are only those that I know of), which I personally consider to be a fairly good level of popularity. Enumerate all the changes and additions included in the assembly for a very long time, if someone is interested, then you can read in detail here .

And finally, I would like to say that the trend, advertising and cloud hosting can certainly give an impression of the advantage of the MODx Revolution branch in many web development issues, but attempts to write off MODx Evolution against this background are quite premature, and today almost any task for Revo can be resolved by Evo. And if you take into account the possibilities of assembly, it is impossible not to admit that the second one even surpasses the first one: convenience, speed of work in the admin panel, the ability to specify CNC names for preview images and some other functions that are not available in Revo yet. But, nevertheless, it is impossible to say that some kind is worse, and some is better - for a long time each branch has become a separate self-sufficient way to solve certain tasks, and what way to choose is to be decided by the developer.

UPD. 03/21/2013
Found a couple of critical errors, below solution:
Conflict with php5.3 (update file manager / includes / protect.inc.php download here )
The manager in the admin panel is not created normally (update the file manager / processors / save_user.processor.php download here )
In his build already fixed GitHub

UPD2. 03/21/2013
MODX 1.0.10RC

UPD3. 04/18/2013
MODX 1.0.10 of 04/18/2013