Can we get a MODx Revolution news update?

It has been almost six months since MODx Revolution - Alpha 6 was released. Can we get a news update on how things are progressing?

Sure.

We’re very close to beta. A few things are left; we’re finishing up touches on locking, resolving some issues with uninstallation of transport packages (specifically reverting to prior package versions), and filling out the documentation. We wont release beta until we feel comfortable with the documentation; we don’t want hundreds of new users stumbling over Revolution without some kind of guidance.

Beta-1 will be a marked difference from alpha-6; the manager has been redesigned, it introduces Property Sets, proper Transport Packaging (including integration to modxcms.com), and many, many more cleanups and enhancements.

Also, we’re having to go and convert a few of the main 3rd Party Components (such as Wayfinder, Breadcrumbs, TinyMCE, etc) to Revo, since the authors are either MIA or have not yet started converting their snippets to Revo.

Once those things are finished, we’ll release beta. The goal was by the end of this month, but again, that’s all dependent on the help we get.

Now, rhat’s refreshing!

Can’t wait

Sounds exciting. Thanks for the news.

How about a screen shot of the redesigned manager?

Quote from: Pixel at May 20, 2009, 09:09 PM

Sounds exciting. Thanks for the news.

How about a screen shot of the redesigned manager?

It’s a small bit out of date - we’ve done a couple cleanups to the accordion trees, but:

http://www.flickr.com/photos/36933895@N02/sets/72157617699130084/

You guys really took this thing to an insane level. This is gonna kick some buts.
I hope the community will help promote it.

Just to confirm, there will be no limitations on the number of pages right?

Can’t wait

Quote from: treigh at May 21, 2009, 03:30 PM

Just to confirm, there will be no limitations on the number of pages right?

Let’s not go hopping and skipping to Oz now. You are still going to have cache limitations per context, so it’s still dependent on how you organize your data and your physical environment, but it will be possible to more easily craft solutions that scale to your needs with Revolution, no doubt.

Ditto on what Jason said.

But to answer what might have been another question - the 5000 doc limit is no longer an issue.

But, like any CMS and any website, if you make it poorly, it will perform poorly. If you make a e-commerce site made of 50,000 Resource pages, then it will be slow. Best in those circumstances are custom tables with that data, along with a memcache implementation, eAccelerator, and other caching enhancements.

All of which are possible in Revolution.

Quote from: splittingred at May 21, 2009, 04:47 PM

But to answer what might have been another question - the 5000 doc limit is no longer an issue.

To be specific, it is possible to have more than ~5000 Resources per Context in Revo by disabling the cache_context_settings for that Context, but that’s a trade-off that ultimately has diminishing returns.  IOW, it’s still always better to distribute and partition data sets into smaller nodes as possible.  If you have a node that must have 5000 Resources in it, you should be considering an alternative way to store and present that data dynamically through a single templatable, optimized view, i.e. a single Resource with a snippet to present an individual row from a custom table with millions or even billions of rows if you wanted.

Great,

Thanks guys for the clarifications