Have fun with joomla then lol, glad i switched joomla with modx years ago.
Evolution user, I like the back-end speed and simplicity
Moderators, will you please remove modxjr1 from this thread. There is a great dialogue going on here and there is no need for flame bait here.
-Noah
-
☆ A M B ☆
- 24,524 Posts
Or at least while some of his points may be close to some of our feelings on the issue, they could be expressed a bit more tactfully. Face it, we're active on this thread because we don't like Revo, and we all have our reasons for the dislike, and for our dismay at the way MODx has gone lately. Hopefully we are all a reasonable and adult group and can express ourselves without being obnoxious about it, although I do admit that I frequently have a warped sense of humor that others do not find quite so amusing.
I ran across something very interesting in researching a question for somebody
An alternative to using eval to mimic include - is to just use include on an in-memory stream. This allows a user-cooked class to pretend it is a stream, so methods which expect a stream or URL will be happy (like include)
i) register a global variable stream wrapper using stream_wrapper_register(). (search the man page for "Example class registered as stream wrapper")
ii) use file_get_contents (or db read or...) to read your php script into a global variable.
eg
$GLOBALS['yourvar']=file_get_contents('somefile.php');
iii) call include with the URL you registered. Using the example wrapper above:
include 'var://yourvar';
-
☆ A M B ☆
- 1,231 Posts
eval() replace to include()? It is interesting!
-
☆ A M B ☆
- 24,524 Posts
In our case, define the stream wrapper for $snippet, fetch the snippet code from the array MODx has already loaded from cache, and include it. No eval(). Same thing could be done for @EVAL TVs, I think.
-
☆ A M B ☆
- 77 Posts
Hello to my fellow MODx colleague,
I know I rarely respond to forum but I wanted to jump in and provide my thoughts. Stefanie, as a user and developer of both EVO and REVO I am aware of the challenges that some users are having in the development of new plugins and adapting to REVO. It is important to understand that like all changes there is opposition, but with change comes invitation and REVO does deliver "CREATIVE FREEDOM".
It is important to not look at EVO and REVO as two separate products but rather think of it more like an upgrade in operating system. Windows XP versus Windows 7 or MAC Leopard versus Lion. They are both operating systems of the same family but to meet the demand of the market a new version was needed. Not just an update.
It is also important to remember that MODx provides it solution as a FREE OPEN SOURCE CMS and for a number of business, and I am guess that is some of you may not even exist if MODx did not make the sacrifices the MODx team has made.
So I just want to remind everyone to say thank you when ever you can and remember most of their time is a sacrifice away from their Family, away from their Kids. That said like all business MODx needs to focus on what efforts are in the best interest on company. Right now EVO does not appear to be apart of that growth strategy.
So lets all be patient and understanding.
-
☆ A M B ☆
- 77 Posts
I what make sure that I am clear I am not saying that the efforts to save EVO is a bad idea. But I am say that there is only so much time in a day and the MODx Team can not be every where. So I know that the team has not been responding at the same rate and level as before but lets face it, with Cloud they have been developing a solution that will benefit us all. Allowing the continued growth and existence of MODx
(thousands of helping posts to testify...)
