Evo or Revo?

I’m not positive about the second part (though If, as I suspect, it came from OpenGeek, you can take it as gospel). The part about making any tag uncached in Revolution is definitely true and will remain so. The ability to control which items are cached when they are nested (e.g., an uncached document containing a chunk tag for a chunk that contains other tags) is notoriously flaky in Evolution.

Quote from: BobRay at Jan 09, 2011, 09:02 PM

I’m not positive about the second part (though If, as I suspect, it came from OpenGeek, you can take it as gospel). The part about making any tag uncached in Revolution is definitely true and will remain so. The ability to control which items are cached when they are nested (e.g., an uncached document containing a chunk tag for a chunk that contains other tags) is notoriously flaky in Evolution.

I should clarify - the second question in my last post I see as more a case of what should be best practice, and only indirectly relevant here. Best practice is something people debate, which is good. I’ve read OpenGeek’s posts on this topic, and see his point. I’ve also read other posts with opposing points of view and see their also valid points - hence my approach of picking a technique that suits the situation. Like many other people I like the flexibility of MODx.

For the first question, I should also clarify as looking at my last post I can see I was more vague than intended and wasn’t clear as to what I was getting at - apols. I’m predominately concerned about the 5000 page limit in Evo and what applies to Revo. If I need to cater for sites in excess of the 5000 page Evo guideline, under what circumstances can I rely on Revolution to run reasonably well with a site content table in excess of this figure? As I mentioned above, I thought that this was something I could rely on, but Sharkbait’s post and the linked thread from his post, leads me to doubt this.

The first question should be easy to answer by someone who knows about Revo’s core. Can we have more than 5000 pages, and if yes, what conditions are there on this, if any?

-- Tim.

related discussion: http://modxcms.com/forums/index.php/topic,18872.msg289674.html#msg289674

You can have 50,000 pages if you like in Evo or Revo. At some point, your site will slow down noticeably. That point will depend on the site’s traffic, the server resources, your caching scheme, the use of accelerators and compression, and the what’s actually on the pages, among other things. Any guesses about exactly how many pages you could have before running into trouble wouldn’t be worth much, but the number would be substantially higher for Revolution than for Evolution.

My 2 cents: if Revo says no limitation on the number of resources, then users should be able to use resource as a primary way to manage documents/blogs/articles as in a typical large CMS, otherwise it’s probably a good dev platform but a seriously limited CMS.

Quote from: jimpsr at Jan 10, 2011, 10:38 PM

My 2 cents: if Revo says no limitation on the number of resources, then users should be able to use resource as a primary way to manage documents/blogs/articles as in a typical large CMS, otherwise it’s probably a good dev platform but a seriously limited CMS.

As i understand..
For small/medium web sites it truly a CMS. by medium i mean to a pretty much big sits but not huge ones.
For larger scale sites you come to the point that you can’t escape integrating your own custom tables and writing your own code leaning on modx’s objects and methods and then it becomes more of a CMF, A Framework for CMS.

Quote from: gOmp at Jan 11, 2011, 03:06 AM

Quote from: jimpsr at Jan 10, 2011, 10:38 PM

My 2 cents: if Revo says no limitation on the number of resources, then users should be able to use resource as a primary way to manage documents/blogs/articles as in a typical large CMS, otherwise it’s probably a good dev platform but a seriously limited CMS.

As i understand..
For small/medium web sites it truly a CMS. by medium i mean to a pretty much big sits but not huge ones.
For larger scale sites you come to the point that you can’t escape integrating your own custom tables and writing your own code leaning on modx’s objects and methods and then it becomes more of a CMF, A Framework for CMS.

Large sites can be very simple in layout (e.g. news portal with several channels and frequent news updates) and the only potential obstacle here preventing these sites from growing is Revo’s potential limitation on resources, nothing else.

Suppose I have to go custom table approach as suggested by some for such a site with 100K+ news entries, with a little bit scripts knowledge, one might be able to populate data from table,but how about I have several editors with different publishing needs? set publishing schedule? comment support? pagination? html editor? then how to navigate through all news entries? how about TV like support for news entries say in the future we decide to have tag support? It’s no easy task and it seems to me this approach is more like writing a custom Modx-like module inside Modx, just does not make sense.

My question is why not just solve this potential resource limitation thing? I bet many current users (especially from editor/design background) will be happy and those who want to have more power out of Revo should also be happy.

The theoretical limit is infinite in Revolution, I guess. Practically (and that will be visible with any CMS or framework) is that at a certain point there’s so much data to go through to find that piece of cache data. With chunks, snippets, placeholders, resource fields, tvs that increases the load time.

I don’t think anyone has hit a practical limit yet, outside of the actual managing of resources in the document tree. Having 100K+ articles in there needs you to really think about how they are going to be categorized in folders in order to keep it clear by the time you reach 100K+. A certain folder structure, automatically created when a new article is added, would seem at the very least a requirement.


But that’s where the flexibility comes in: it’s all possible to implement without changing one line of core code.


The topic Sharkbait linked to gives some nice insights in the caching, definitely worth to check out.

I think that when you get into 100K+ you must have some kind of balance loading, maybe serve the content from different domains/servers or have a really powerful dedicated server

Quote from: cyclissmo at Nov 04, 2010, 02:44 PM

At this point I would recommend Revolution for any first-time Modx’ers. Evolution will be maintained, but Revo will only continue to improve.

Mike

OK, it’s the day before nailing geezer to bit of wood, so I’ve got a bit of conceptual time rather than pixel mining.

I am struggling with this. I am new to CMS, I’ve been lurking for a year and finally plumped for gaining indepth knowledge of MODx so I’m here for the long haul. Being new, I chose the latest. After building my first site I am finding that a few of my gripes are not just mine and maybe I should consider going to Evolution.

Main complaints;

Revolution is very very slow to deliver manager stuff. It’s not particularly fast at delivering the pages either.
The lack of a front end editor - I know it will come but I am dreading the phone conversations to get my client up to speed with using Manager
The complexity of the security system and access permissions, I also have spent half a day with "access denied" messages and I’m a bit wary of getting back there.

I don’t know Evolution at all, it seems a bit annoying that there is no easy path for a site made in one to be ported to the other.

so....

should I stay? or should I learn Evolution, knowing that a year down the line I will probably want to go back to Revolution?