Modx vs ExpressionEngine

From first look, it appears ExpressionEngine is something Modx is heading towards - a multi-purpose everything framework ? What most of us would be interested in is a multi-framework we can use for everything, blogs, mai lists, forums, website etc instead of having to use mutliple software.

http://expressionengine.com/overview/features/

Yeah I know EE I have used it for 2 years for my blog... great software, but cluttered admin IMHO and MODx is more flexible... I don’t have time (leaving for w-e) but I’ll get back here with a more detailed comparison...

Not to mention that Expression Engine isn’t free whereas MODx is.

But EE is really nice and their site redesign is incredible. Good stuff really, but not the same thing as MODx. I think MODx is more like a blend of Code Igniter and EE.

Well i think that modx 0.9.7 new manager will surpass expression engine and immersecms.
I’ve played with expression engine a while (the free version) and the fact that you use templates as different "folder" from modx is very strange and sometimes irritating .
I hope that modx 0.9.7 will start to have a good documentation for the framework. Something like the one from codeignitor would be great cause that one is super

I’ve inherited several EE sites, and you can’t argue that EE is full-featured and well-documented. What I don’t like about EE is the following:
In EE, EVERYTHING is a blog post in a weblog. By default, EE does not provide the nice Folder/document structure view that MODx has. I like to think of my content as living in certain places, and MODx lets me do that.
In EE, your templates have content. In MODx, you choose how your content is viewed. So in MODx, you open up a page, then you select which template that page will use. In EE, you build a template, then within that template you specify which content that template will display. This is a simplification, and both systems have ways of extending or overriding that behavior, but for most of the sites that I’ve worked on, MODx just made more sense.

Isn’t Code Igniter built by the same folks as EE? Ellis Labs?

Yes it is and Expression Engine 2.0 is built upon CodeIgniter, EllisLab is betting that this will attract CodeIgniter developpers to EE and boost plugins creation. That’s a very smart move, and the EE 2.0 video was really a big step up from the current release... we shall see.

MODx could get a lot of mileage out of promoting the xPDO stuff... write some really solid documentation (preferably run it by someone who isn’t an expert in that stuff and see if they can stumble through it). Some videos would be a godsend, and I’d suggest using more clear names... lord, xPDOObject doesn’t tell me a thing about what the heck that object is or why I’d want to extend it. Little things like that just make it more difficult to understand.

What I’d love to see in MODx is the ability to define arbitrary tables... e.g. "Store Locations", and then the manager could control the CRUD access to edit/update the address, city, state, and phone fields. You can emulate this with Template Variables, but it’s not 100% clean when it comes to the database architecture. Expression Engine offers more flexibility there, but it’s not all that clean either. A GUI front end for defining table relations would just be amazing... I’ve only really seen it in Filemaker... ha.

Quote from: Everettg_99 at Dec 13, 2008, 04:41 PM

MODx could get a lot of mileage out of promoting the xPDO stuff... write some really solid documentation (preferably run it by someone who isn’t an expert in that stuff and see if they can stumble through it). Some videos would be a godsend, and I’d suggest using more clear names... lord, xPDOObject doesn’t tell me a thing about what the heck that object is or why I’d want to extend it. Little things like that just make it more difficult to understand.

It’s an xPDOObject, so it is providing what ever user-defined class you want to build with xPDO access to all the methods it provides. This is much like PHP’s stdObject, though every object implicitly extends stdObject in order to gain access to it’s methods, whereas xPDO requires that your classes explicitly extend xPDOObject. As I said in the other topic, nothing good documentation won’t cure...

Quote from: Everettg_99 at Dec 13, 2008, 04:41 PM

What I’d love to see in MODx is the ability to define arbitrary tables... e.g. "Store Locations", and then the manager could control the CRUD access to edit/update the address, city, state, and phone fields. You can emulate this with Template Variables, but it’s not 100% clean when it comes to the database architecture. Expression Engine offers more flexibility there, but it’s not all that clean either. A GUI front end for defining table relations would just be amazing... I’ve only really seen it in Filemaker... ha.

This is the vision, to have visual and programmatic editing and lifecycle-maintenance tools in MODx/xPDO for user-defined domain models reverse-engineered from existing databases and/or generated along with new custom database designs, in a way that makes it easy to develop and maintain applications, manage data structures and relationships, and even share data across various storage engines. We’re only part of the way there, but hopefully, what we’ve done with xPDO already (i.e. developing MODx Revolution 2.0, and other projects that we’ll hopefully be able to turn into case studies) will attract the attention of enough PHP developers, UI designers, and technical writers, and others interested in contributing to the effort to make that vision a reality sooner than later.

This seems an appropriate place, but one area where MODx beats Expression Engine hands down is the ability to find what code is handling a particular url. Say you’ve got something like mydomain.com/path/to/page... in MODx, it’s really obvious that you’d go looking in a folder named "path" for a sub-folder named "to" where you could find a page named "page"... maybe you’d have to examine the template code and its associated chunks to find the exact bit of code you needed to change, but it’s a very simple and direct process for finding the code that is used to handle any given url.

In Expression Engine, you have template groups that contain templates... the template manager has a search feature, but in my opinion, its implementation is very difficult to use by comparison. In the EE sites I’m maintaining, the act of merely FINDING the code I need to change has been the single biggest time-suck. EE reminds me of the Windows Registry... it’s kinda like a black box... some things are straight-forward, but there are enough caveats to drive you crazy. EE isn’t as bad as the Registry, but I never had that amount of trouble finding things using MODx.