When posting this discussion I acknowledge I'm committing the cardinal sins of posting a non-support question in the 'Discussion' thread and advocating a new version Evo.
Whilst clearly Rev is the future of MODX and in many regards is superior to Evo, it has to said that Rev isn't for everyone. I've just updated one of my small sites and the choice of CMS was between Evo and Drupal. Increasingly I'm finding it harder to justify choosing a CMS that no longer seems to be developed.
I fully appreciate supporting two CMS is stretching MODX's resources to its limits but could not a new version of Evo 'only' fix bugs and any security problems?
-
☆ A M B ☆
- 24,524 Posts
Evo is still being supported, it's just that so far nothing significant has been added or modified. There are no known security problems (there would be announcements on the Security forum if there were) and no known significant bugs at this point, at least as far as I know.
http://tracker.modx.com/projects/evo
https://github.com/modxcms/evolution
Looking at the list of bugs there are many listed as critical and major priority but unresolved for over a year.
One of your excellent tutorials gives a demonstration of the use of the @INHERIT Binding - try using it with 1.0.5 and it crashes the site. For this reason I still use 1.0.4 but that doesn't have the security fix that 1.0.5 has.
[ed. note: randall last edited this post 14 years, 8 months ago.]
-
☆ A M B ☆
- 24,524 Posts
Um... my site is built on 1.0.5 and uses @INHERIT extensively. Can you give a link to the exact demonstration that crashes?
-
☆ A M B ☆
- 24,524 Posts
I see, it was a change in how an expression following the @INHERIT string was parsed. There are a couple of ways of patching the manager/includes/tmplvars.commands.inc.php file, from replacing the line 80 with the corresponding line from the 1.0.4 version or a suggested replacement of the regular expression alone. These are mentioned in the bug tracker.
Until an update is released, anyway.
yes, I confirm the @INHERIT bug in 1.0.5
