MODx Revolution 2.0.0-beta-5 rev6224 Review

I just came back from a much needed vacation and saw the new release of Revo which made me go "hell yeah!". I’ve been waiting a long time to give it a try now when its out in beta (I couldn’t install the alpha for some reason).

After been reading up on Revo: how fast it was, better cache, new xPDO, QA (programming guidelines - like validating html and write correct cross-browser code) I had high expectations.

My initial reactions with the manager was "confused... ah, this seems quite familiar, it’s Evo with a makeup". The makeup, however, isn’t very appealing - dark and gloomy with an appaling green color, and alot of extra design (every element is css:ed eg. input, textarea, etc...).
My validator plugin says 8 errors (like deprecated attributes for the doc type and alot of "&" errors) which isn’t the code standard I’d expect if I had guidelines. I also get 2 javascript errors within 2 minutes of clicking around.

I can accept all of those things - the css which breaks apart (even in FF), some js which isnt 100% ok, poor usability, my apache crashing twice - since its a beta. But the thing which really is a big issue for me is the load time for the manager: 7.36 sec! And the average is like 5 sec per page??

I’m all for modx and the new redesign but why all the ajax and js in the manager?

I really hope the real deal will be faster in manager mode even if it takes some redesign like dropping some features eg. in the navigation menu.

Looking forward to the next release...

Hello johansalllarsson,

Thanks for your feedback.

The new Revo Manager is built on top of Extjs and therefore will have a lot of nested tables and all of it has css references scattered all the way.
The css theme itself is not yet finished and need a lot of cleanup (It is definitevely not cross browser compliant yet).

The 8 errors might have been reported in Jira, if the MODx team encourage you to report it on the bug tracker and propose a fix if possible.

Concerning the weight, extjs is heavy and can be long to load. You can reduce time by checking in the system setting if you have "compress javascript" activated.

Since it’s beta, there a lot of work still to do to improve the performance.
I don’t think it will be possible to reach the speed of Evolution Manager though.

Quote from: johansalllarsson at Feb 11, 2010, 03:41 PM

My initial reactions with the manager was "confused... ah, this seems quite familiar, it’s Evo with a makeup". The makeup, however, isn’t very appealing - dark and gloomy with an appaling green color, and alot of extra design (every element is css:ed eg. input, textarea, etc...).
My validator plugin says 8 errors (like deprecated attributes for the doc type and alot of "&" errors) which isn’t the code standard I’d expect if I had guidelines. I also get 2 javascript errors within 2 minutes of clicking around.

Feel free to file bugs on the markup here: http://bugs.modxcms.com/

As for the design; well, it was community contributed. It also runs ExtJS, which does a lot of the CSS formatting.

You shouldn’t be getting Javascript errors. What browser are you using?

I can accept all of those things - the css which breaks apart (even in FF), some js which isnt 100% ok, poor usability, my apache crashing twice - since its a beta. But the thing which really is a big issue for me is the load time for the manager: 7.36 sec! And the average is like 5 sec per page??

By poor usability, you mean 508 standards?

Apache crashing twice is not normal. It sounds like you have a faulty PHP or MySQL installation on your server.

Those load times, as well, are not normal. Mine runs about 1-3 seconds per page load. This sounds like you’re having a server error of some sort.

I’m all for modx and the new redesign but why all the ajax and js in the manager?

To increase functionality, such as drag/drop reordering, inline validation, drag/drop of Resources/Elements into content, ajax "stay-in-place" saving, Quick Update/Create, etc. You’ll find the more you use it, the faster your workflow is. You can create an entire minisite, usually, without having to reload the page once.

Most people here who’ve used it have said the same thing - it feels slower at first, but after using it for a while, they never want to go back. Evo will feel sluggish.

Thanks for your feedback.

You shouldn’t be getting Javascript errors. What browser are you using?

Firefox 3.5.7

By poor usability, you mean 508 standards?

I’m unfamiliar with the 508 standards, but I’m guessing it’s some accessibility standards like WCAG. I was more refering to language, placement of elements, administrative forms styled to "unrecognition", response time, workflow etc rather than global accesibility (which would be 0 since the js requirement). Basically It should be so easy and intuitive that I don’t have to think.

Apache crashing twice is not normal. It sounds like you have a faulty PHP or MySQL installation on your server.Those load times, as well, are not normal. Mine runs about 1-3 seconds per page load. This sounds like you’re having a server error of some sort.

It’s the first time it crashed. I have an Evo which doesn’t crash. I have to say I’m not using top notch stuff either: Windows + XAMPP without compression and eaccelerators. But, when i produce a song I never listen it on my $2000 studio speakers since it will always sound good. I test it on some old computer speakers - if it sounds good in those it will sound good in any stereo. I apply the same idea to programming. However, it could be something wrong with my dev. environment. I’ll check it up this weekend.
For now its 5-10 sec for Revo and 1.3 sec for Evo with this dev. env.

To increase functionality, such as drag/drop reordering, inline validation, drag/drop of Resources/Elements into content, ajax "stay-in-place" saving, Quick Update/Create, etc. You’ll find the more you use it, the faster your workflow is. You can create an entire minisite, usually, without having to reload the page once.

Well its good to increase functionality, as long as it adds value to the product (eg. first page (dashboard) drag and drop serves 0 value for me atleast). Each click was a reload for me (create resource/edit resource) which took ages since it had to load, via js, php scripts and then via js reorder html elements, add on click events and other js functions to elements.

Most people here who’ve used it have said the same thing - it feels slower at first, but after using it for a while, they never want to go back. Evo will feel sluggish.

I’m just afraid that first impressions might make people reject the platform.

Well, since there might be something wrong with my php/mysql I might change my mind this weekend...

I use MODx in every project I can and I’d really like to see Revo rise to the occasion so I can boast about it among my .net and java colleagues

The 8 errors might have been reported in Jira, if the MODx team encourage you to report it on the bug tracker and propose a fix if possible.

Feel free to file bugs on the markup here: http://bugs.modxcms.com/

I’ll test it this weekend again and report any bugs and/or issues.

Quote from: johansalllarsson at Feb 11, 2010, 06:11 PM

It’s the first time it crashed. I have an Evo which doesn’t crash. I have to say I’m not using top notch stuff either: Windows + XAMPP without compression and eaccelerators. But, when i produce a song I never listen it on my $2000 studio speakers since it will always sound good. I test it on some old computer speakers - if it sounds good in those it will sound good in any stereo. I apply the same idea to programming. However, it could be something wrong with my dev. environment. I’ll check it up this weekend.
For now its 5-10 sec for Revo and 1.3 sec for Evo with this dev. env.

I would take a look at your PDO drivers, and your mysql client+server numbers. I think some people have reported XAMPP on win having faulty versions of MySQL. (I may be wrong.)

I’m just afraid that first impressions might make people reject the platform.

If that was true, no one would be using Drupal or Joomla.

Thanks for your impressions.

Quote from: splittingred at Feb 11, 2010, 06:25 PM

I would take a look at your PDO drivers, and your mysql client+server numbers. I think some people have reported XAMPP on win having faulty versions of MySQL. (I may be wrong.)

I’m just afraid that first impressions might make people reject the platform.

If that was true, no one would be using Drupal or Joomla.

LOL.

I’m using XAMPP on Vista with FF 3.5.7 and I almost never have Manager load times over a second or two. IIRC, I did have to downgrade from my last XAMPP install back to the previous version and I think I may have downloaded a MySQL .dll file somewhere a while back clear up some problems I was having.

Before messing with your configuration, however, try Google Chrome and see how the speed is. If Chrome is fast, then you may have a FF add-on issue.

If that was true, no one would be using Drupal or Joomla.

Haha

johansalllarsson,

I’d certainly look at your environment, I’d also look to make sure you don’t have your browser cache off either. Reloading EXTS would certainly slow page loads.

As far as the manager theme is concerned, some people don’t like the dark, UI, some people don’t like light UI’s. For example my dev environment, my Textmate is light text on a #111111 background but I find it easier to use.. That being said I think a light, lower contrast theme might look nice.

We are more than happy to review specific improvements an can always have more eyes on QA for errors and etc. Keep testing and sharing your experiences and report those bugs.

I checked it again with a ’real’ apache, the result was 3.64s (onload: 1.31s). Much better result than xampp+ff w. alot of plugins.